I am seeing what looks like a possible routing loop or some other routing issue 
going on with Comcast’s backbone in Ashburn, VA. I am a customer in Western 
Pennsylvania and I am unable to reach certain destinations such as 
www.duckduckgo.comor www.google.org. This has been going on for about an hour 
afaik. Traceroutes are playing ping pong between 
cr2.ashburn.va.ibone.comcast.netand either cs2 or 
cs4.ashburn.va.ibone.comcast.net

An example MTR to www.duckduckgo.com.

HOST: gravitron Loss% Snt Last Avg Best Wrst StDev
1.|-- IRIDIUM 0.0% 100 0.7 0.9 0.6 6.8 0.7
2.|-- 96.120.62.193 0.0% 100 8.0 9.4 7.4 15.3 1.9
3.|-- 96.108.98.65 0.0% 100 8.9 9.7 7.3 19.4 2.2
4.|-- 162.151.65.5 0.0% 100 9.8 10.3 5.6 17.3 1.9
5.|-- be-7016-cr02.ashburn.va.i 0.0% 100 18.5 17.3 15.1 23.9 1.8
6.|-- be-1402-cs04.ashburn.va.i 98.0% 100 15.2 15.3 15.2 15.5 0.2
7.|-- be-1402-cr02.ashburn.va.i 97.0% 100 22.1 18.7 16.4 22.1 3.0
8.|-- ??? 100.0 100 0.0 0.0 0.0 0.0 0.0
9.|-- be-1402-cr02.ashburn.va.i 94.0% 100 18.2 17.7 16.2 21.4 1.9
10.|-- be-1402-cs04.ashburn.va.i 99.0% 100 18.3 18.3 18.3 18.3 0.0
11.|-- be-1402-cr02.ashburn.va.i 94.0% 100 18.7 20.2 16.1 30.4 5.1
12.|-- ??? 100.0 100 0.0 0.0 0.0 0.0 0.0
13.|-- be-1402-cr02.ashburn.va.i 93.9% 98 18.1 18.6 16.8 24.2 2.8
14.|-- ??? 100.0 96 0.0 0.0 0.0 0.0 0.0
15.|-- be-1402-cr02.ashburn.va.i 96.9% 96 16.7 17.6 16.7 18.7 1.0
16.|-- ??? 100.0 83 0.0 0.0 0.0 0.0 0.0
17.|-- be-1402-cr02.ashburn.va.i 95.2% 83 16.9 18.5 16.9 20.5 1.9
18.|-- ??? 100.0 65 0.0 0.0 0.0 0.0 0.0
19.|-- be-1402-cr02.ashburn.va.i 96.9% 65 17.5 17.0 16.6 17.5 0.6
20.|-- ??? 100.0 54 0.0 0.0 0.0 0.0 0.0

I have no way of knowing if this is isolated to the mid-Atlantic region or if 
it’s a widespread issue. Interestingly enough, Downdetector is showing a large 
spike in down reports across a wide range of services all at the same time.

Is anyone else experiencing this?


--
Geoff
AB3LS
_______________________________________________
Outages mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages

Reply via email to