Unable to geto to www.cymru.com and 126.96.36.199 has been down for 5+ hours. Known issue?
I think Ameritech/SBC/AT&T has problems here in Chicago. We have had
problems getting to several sites here. Traces across Ameritech's
network die in some spots. We are trying to get the issues resolved,
but Ameritech's people are...less than clueful.
www.cymru.com resolves to 188.8.131.52 which is reachable from AS1103.
Getting hung up in savvis - can't ping through -
Odd - I am seeing my route die here (from AS7949):
1 router-sf-t3sf.wmis.net (184.108.40.206) 4 msec 8 msec 4 msec
2 220.127.116.11 [AS 12129] 4 msec 12 msec 4 msec
3 edge-1.sfld-mi.123.net (18.104.22.168) [AS 12129] 4 msec 4 msec 4 msec
4 POS2-1.GW4.DET5.ALTER.NET (22.214.171.124) [AS 701] 8 msec 8 msec 4 msec
5 500.at-6-3-0.CL2.DET5.ALTER.NET (126.96.36.199) [AS 701] 8 msec 8 msec 4 msec
6 0.so-5-0-0.XL2.BOS4.ALTER.NET (188.8.131.52) [AS 701] 40 msec 40 msec 36 msec
7 0.so-7-0-0.XR2.BOS4.ALTER.NET (184.108.40.206) [AS 701] 48 msec 36 msec 40 msec
8 178.at-3-0-0.HR1.BOS4.ALTER.NET (220.127.116.11) [AS 701] 36 msec 40 msec 36 msec
9 0.so-0-2-0.AR1.BOS24.ALTER.NET (18.104.22.168) [AS 701] 36 msec 40 msec 36 msec
10 * * *
My BGP session to cymru has been down 5hs33min
just to through more fuel on the fire, from a 701 perspective it hops
though savvis and dies here:
I think this is the upstream device to the 'customer' network... perhaps
firewall problems? or a local host problem. Generally they are pretty
quick to fix these sorts of things.
Maybe its just _scary_ Halloween routing?
It works from my view of SBC/Ameritech... even though it looks like its going through a Cisco Systems customer connection.
6 ex1-g9-0-0.pxatga.sbcglobal.net (22.214.171.124) 17.078 ms 16.964 ms 16.89
7 bb2-p3-0.atlnga.sbcglobal.net (126.96.36.199) 17.586 ms 75.782 ms 17.365
8 bb1-p14-0.atlnga.sbcglobal.net (188.8.131.52) 17.599 ms 17.469 ms 17.37
9 core1-p5-0.cratga.sbcglobal.net (184.108.40.206) 17.232 ms 17.243 ms 17.2
10 core3-p3-0.crchil.sbcglobal.net (220.127.116.11) 31.975 ms 31.739 ms 31.
11 core1-p9-0.crchil.sbcglobal.net (18.104.22.168) 32.315 ms 32.086 ms 31.9
12 bb1-p6-0.chcgil.ameritech.net (22.214.171.124) 66.854 ms 33.085 ms 110.77
13 ded2-g1-3-0.chcgil.ameritech.net (126.96.36.199) 33.132 ms 64.020 ms 33
14 Cisco-Systems-1054141.cust-rtr.ameritech.net (188.8.131.52) 41.344 ms 37.3
96 ms 37.158 ms
Christopher L. Morrow wrote:
So, how many people from nanog DOES it take to troubleshoot a simple
network outage anyways?
With each passing day I find myself wishing more and more that there was a
Cisco Certified Traceroute Engineer program, and a convenient system to
ignore emails with traceroutes from anyone else.
] Unable to geto to www.cymru.com and 184.108.40.206 has been down
] for 5+ hours. Known issue?
We brought up a new BGP peer today, oddly enough to add additional
redundancy and improved performance. The turn-up appears to
have gone awry somewhere in the provider's network, and we're
debugging that now. The primary site has been online the entire
time, but the routing oddness has caused everyone a bit of pain.
We are also seeing some Chicago-based oddness that others are
enduring. We're pretty sure it has nothing to do with one of our
members, an ardent Cubs fan, cursing the Sox.
We continue to debug it with our peers. Stay tuned!
Apologies for the inconvenience.
] Maybe its just _scary_ Halloween routing?
It's definitely Halloween, but this isn't as scary as it looks.
Back when we were part of Cisco, SBC named our link to them
accordingly. Now that we're on our own, I should probably ask
them to change that.
ah-ha! me thinks someone is in the midst of a new customer turnup, though
it's back to replying to tcp/80 requests via savvis now.
Just a quick interruption in your day to update you on the routing
fun we had. The problem was two-fold:
1. An errant provider router that randomly selected which
prefixes to propagate. Mix that with uRPF, and you
have FUN FUN FUN!
2. An interesting use of LOCAL_PREF by the provider, now
Our tests from multiple external pods and route servers show that
we're globally visible again. If you're having any difficulty
reaching us, please let us know at <firstname.lastname@example.org>.
Again we apologize for the inconvenience!
Rob, for Team Cymru.