New Contributor
•
4 Messages
Is Comcast having a routing issue?
Browser can't reach amazon.com's site; and running ping shows following output; so does comcast have a loop in routing? And that is why I can't reach Amazon? Referring to lines 6 through 30; thanks.
# tracepath amazon.com
1?: [LOCALHOST] pmtu 1500
1: router.asus.com 0.513ms
1: router.asus.com 0.457ms
2: 99-99-99-999-static.hfc.comcastbusiness.net 7.152ms
3: 99.999.999.99 17.642ms
4: xe-5-3-0-sur01.newmexiconw.dc.bad.comcast.net 72.712ms asymm 5
5: ae-28-0-ar01.capitolhghts.md.bad.comcast.net 32.745ms
6: be-33657-cr02.ashburn.va.ibone.comcast.net 37.238ms
7: be-10142-pe01.ashburn.va.ibone.comcast.net 27.128ms
8: no reply
9: be-10142-pe01.ashburn.va.ibone.comcast.net 24.681ms asymm 7
10: no reply
11: be-10142-pe01.ashburn.va.ibone.comcast.net 25.156ms asymm 7
12: no reply
13: no reply
14: no reply
15: be-10142-pe01.ashburn.va.ibone.comcast.net 29.478ms asymm 7
16: no reply
17: no reply
18: no reply
19: be-10142-pe01.ashburn.va.ibone.comcast.net 31.963ms asymm 7
20: no reply
21: be-10142-pe01.ashburn.va.ibone.comcast.net 24.495ms asymm 7
22: no reply
23: be-10142-pe01.ashburn.va.ibone.comcast.net 24.885ms asymm 7
24: no reply
25: no reply
26: be-10142-cr02.ashburn.va.ibone.comcast.net 17.707ms asymm 6
27: no reply
28: no reply
29: be-10142-pe01.ashburn.va.ibone.comcast.net 22.378ms asymm 7
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
Cross-post: http://unix.stackexchange.com/questions/317625/how-to-interpret-ping-output-when-output-loops
ZLASupport
Visitor
•
4 Messages
9 years ago
Hello,
I am having similar issues in Philadelphia areas. I am able to get to most sites however having issues with sites like livechat.com.
I think Comcast is having some BGP issues still, just a thought unless someone can tell me otherwise.
When I enable my Comcast link, users start complaining very fast.
Here is my traceroute:
traceroute to google.com (216.58.195.142), 64 hops max, 52 byte packets
1 192.168.28.1 (192.168.28.1) 1.666 ms 3.811 ms 1.378 ms
2 173-161-232-134-philadelphia.hfc.comcastbusiness.net (173.161.232.134) 5.507 ms 3.673 ms
3 96.120.78.113 (96.120.78.113) 15.863 ms
b3329.phlapa-lcr-22.verizon-gni.net (130.81.30.166) 80.413 ms
b3329.phlapa-lcr-21.verizon-gni.net (130.81.30.164) 71.926 ms
4 68.85.152.229 (68.85.152.229) 20.433 ms 18.496 ms *
5 * be-22-ar03.norristown.pa.panjde.comcast.net (69.139.192.149) 26.055 ms
be-22-ar03.newcastle.de.panjde.comcast.net (69.139.192.145) 29.715 ms
6 0.et-9-1-0.gw13.iad8.alter.net (140.222.235.213) 15.529 ms
hu-0-11-0-0-ar03.ivyland.pa.panjde.comcast.net (68.85.159.237) 111.594 ms 18.812 ms
7 204.148.79.46 (204.148.79.46) 78.311 ms 100.264 ms
be-33287-cr02.newyork.ny.ibone.comcast.net (68.86.93.173) 62.244 ms
8 * 216.58.215.38 (216.58.215.38) 92.127 ms
hu-0-11-0-0-pe02.111eighthave.ny.ibone.comcast.net (68.86.85.18) 27.129 ms
9 50.248.116.186 (50.248.116.186) 28.842 ms
72.14.233.95 (72.14.233.95) 83.788 ms
50.248.116.186 (50.248.116.186) 53.424 ms
10 209.85.245.116 (209.85.245.116) 187.738 ms
iad23s24-in-f14.1e100.net (216.58.195.142) 103.762 ms
209.85.245.116 (209.85.245.116) 93.674 ms
0
0
rxman4453
New Member
•
2 Messages
9 years ago
I'm having routing issues as well. The issue is not with my home but with the network after it leaves my home. When I run pingplotter to Google's DNS servers or many others I have dropped packets. And I would not be worried about it if it wasn't affecting the final destination but it is. I have called and notified Comcast with no resolution 😞
0
0