Forum Home
PC World Chat
 
Thread ID: 121746 2011-11-10 18:14:00 International bottleneck today Paul.Cov (425) PC World Chat
Post ID Timestamp Content User
1242886 2011-11-10 18:14:00 Problems today...

tracert www.urbandictionary.com

Tracing route to proxy.heroku.com [50.16.233.102]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 31 ms 31 ms 31 ms 10gi6-0-0-100.bras1ldv.akl.vf.net.nz [203.109.12
9.41]
3 29 ms 30 ms 30 ms be7.ppnzldv02.akl.vf.net.nz [203.109.180.242]
4 31 ms 31 ms 30 ms be8.ppnzldv01.akl.vf.net.nz [203.109.180.241]
5 156 ms 156 ms 156 ms ip-141.199.31.114.VOCUS.net.au [114.31.199.141]

6 156 ms 156 ms 160 ms 10gigabitethernet3-2.core1.sjc1.he.net [64.71.18
4.45]
7 * * * Request timed out.
8 234 ms 227 ms 226 ms 10gigabitethernet9-3.core1.ash1.he.net [184.105.
213.178]
9 227 ms 281 ms 226 ms 209.51.161.42
10 228 ms 227 ms 228 ms 72.21.220.47
11 228 ms 284 ms 227 ms 72.21.222.155
12 229 ms 227 ms 227 ms 216.182.224.93
13 * * * Request timed out.
14 * * * Request timed out.
15 234 ms 237 ms 228 ms ec2-50-16-233-102.compute-1.amazonaws.com [50.16
.233.102]

Trace complete.


Tracing route to www.amazon.com [72.21.214.128]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 47 ms 32 ms 30 ms 10gi6-0-0-100.bras1ldv.akl.vf.net.nz [203.109.12
9.41]
3 29 ms 30 ms 29 ms be7.ppnzldv02.akl.vf.net.nz [203.109.180.242]
4 31 ms 31 ms 31 ms be8.ppnzldv01.akl.vf.net.nz [203.109.180.241]
5 155 ms 155 ms 156 ms ip-141.199.31.114.VOCUS.net.au [114.31.199.141]

6 159 ms 156 ms 166 ms 10gigabitethernet3-2.core1.sjc1.he.net [64.71.18
4.45]
7 * * * Request timed out.
8 234 ms 226 ms 227 ms 10gigabitethernet9-3.core1.ash1.he.net [184.105.
213.178]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete (but sod-all else is complete) 		Paul.Cov (425)
1242887 2011-11-10 18:37:00 Works OK here. Snorkbox (15764)
1242888 2011-11-10 19:17:00 They all load for me. Bobh (5192)
1242889 2011-11-10 19:35:00 NP here.
:) 		Trev (427)
1242890 2011-11-10 21:07:00 You think that's bad? I've managed to end up with my bandwidth shaped to 64k for the next two weeks :crying

Have to load one site at a time. If that. 		Agent_24 (57)
1242891 2011-11-10 21:10:00 Your end methinks ... all load without problem. SP8's (9836)
1242892 2011-11-10 23:57:00 no, not his end - all timeouts are at 10gigabitethernet9-3.core1.ash1.he.net

yes, both sites load ok, but what OP is looking at is the tracert..

and my results are pretty much exactly the same...


Tracing route to proxy.heroku.com [184.73.173.41]
over a maximum of 30 hops:

1 11 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 52 ms 53 ms 52 ms e0-0-622.tim-bcl-core1.ihug.net [203.109.129.149
]
3 51 ms 51 ms 51 ms 203.109.129.150
4 59 ms 59 ms 59 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2
09]
5 60 ms 59 ms 59 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2
09]
6 194 ms 195 ms 196 ms ip-141.199.31.114.VOCUS.net.au [114.31.199.141]

7 196 ms 197 ms 198 ms 10gigabitethernet3-2.core1.sjc1.he.net [64.71.18
4.45]
8 * * * Request timed out.
9 265 ms 267 ms 270 ms 10gigabitethernet9-3.core1.ash1.he.net [184.105.
213.178]
10 266 ms 266 ms 270 ms 209.51.161.42
11 285 ms 267 ms 267 ms 72.21.220.43
12 267 ms 266 ms 265 ms 72.21.222.145
13 267 ms 266 ms 267 ms 216.182.224.55
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 266 ms * 265 ms ec2-184-73-173-41.compute-1.amazonaws.com [184.7
3.173.41]

Trace complete.

C:\Documents and Settings\Boss>tracert www.amazon.com

Tracing route to www.amazon.com [72.21.194.1]
over a maximum of 30 hops:

1 77 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 64 ms 52 ms 53 ms e0-0-622.tim-bcl-core1.ihug.net [203.109.129.149
]
3 52 ms 51 ms 51 ms 203.109.129.150
4 59 ms 60 ms 59 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2
09]
5 60 ms 59 ms 59 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2
09]
6 195 ms 196 ms 196 ms ip-141.199.31.114.VOCUS.net.au [114.31.199.141]

7 200 ms 199 ms 200 ms 10gigabitethernet3-2.core1.sjc1.he.net [64.71.18
4.45]
8 * * * Request timed out.
9 266 ms 266 ms 272 ms 10gigabitethernet9-3.core1.ash1.he.net [184.105.
213.178]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Documents and Settings\Boss>tracert www.amazon.com

Tracing route to www.amazon.com [72.21.194.1]
over a maximum of 30 hops:

1 28 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 52 ms 53 ms 51 ms e0-0-622.tim-bcl-core1.ihug.net [203.109.129.149
]
3 52 ms 52 ms 51 ms 203.109.129.150
4 60 ms 59 ms 58 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2
09]
5 60 ms 59 ms 59 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2
09]
6 195 ms 195 ms 196 ms ip-141.199.31.114.VOCUS.net.au [114.31.199.141]

7 196 ms 196 ms 195 ms 10gigabitethernet3-2.core1.sjc1.he.net [64.71.18
4.45]
8 * * * Request timed out.
9 266 ms 266 ms 270 ms 10gigabitethernet9-3.core1.ash1.he.net [184.105.
213.178]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


BUT this can be from other reasons than "network problems"

here's a couple of possibilities from here (networking.ringofsaturn.com) for example


Another caveat of traceroute is that ICMP, which is the protocol traceroute relies on to get responses from each hop, is usually the lowest priority protocol. So if one router is really busy it might decide to drop ICMP messages, and you will see lots of packet loss, but that router might be forwarding on more common, higher priority traffic just fine.

Also, some sites will filter ICMP for various reasons, so it might appear in a traceroute that a site might be unreachable, but in fact it is reachable.

and


....Just remember that such a traceroute can also be an example of a firewall that is filtering packets, or a router that throws away the kinds of packets that traceroute depends on when it gets overloaded. 		bevy121 (117)
1242893 2011-11-11 01:09:00 Those traceroutes don't appear to indicate any problems at all. Not all servers reply to ping. www.amazon.com appears not to, hence the traceroutes (which use the same ICMP Echo Request packets as ping) time out after the final hop.

The web page loads fine here, and if it does not for you, that is a separate problem unrelated to the traceroute.

Your ping times look reasonable and don't seem to indicate any severe congestion. 		george12 (7)
1242894 2011-11-11 01:34:00 are you with telecom by any chance? icow (15313)
1242895 2011-11-11 01:57:00 You think that's bad? I've managed to end up with my bandwidth shaped to 64k for the next two weeks :crying

Have to load one site at a time. If that.

Here have some of ours. :D

3361 		CYaBro (73)
1 2