Does anyone know what is going on with XO and their peering? My XO circuit is taking weird paths to other carriers, and internethealthreport.com shows elevated latency on all of their links. XO won't tell me anything. This also seems to be affecting US LEC, but I think US LEC buys transit from XO. Appreciate any help, -Scott ------------------------------------------------------------------------ ------------ Scott Berkman CCNP 404-975-0097 Network Engineer scott.berkman@reignmaker.net
Berkman, Scott wrote:
Does anyone know what is going on with XO and their peering? My XO circuit is taking weird paths to other carriers, and internethealthreport.com shows elevated latency on all of their links.
Latency looks fine - Network availability is pretty pathetic. I can route out our XO pipe fine, although there isn't a whole lot on it. I can't make mtr do anything funky that would indicate a problem with XO so I could open a ticket. David
Does anyone know what is going on with XO and their peering? My XO circuit is taking weird paths to other carriers, and internethealthreport.com shows elevated latency on all of their links.
Latency looks fine - Network availability is pretty pathetic. I can route out our XO pipe fine, although there isn't a whole lot on it. I can't make mtr do anything funky that would indicate a problem with XO so I could open a ticket.
Does anyone else miss the good old days when nanog readers/attendees knew why pinging the routers you saw in a traceroute directly was not an accurate measurement of anything? How about when people used diagnostic tools that told you more than "oh crap 91ms from *somewhere* on xo to *somewhere* on xo, omgrotfwtflolz the square is red and I'm pinging 10 quick post to nanog!"? Anyone? I think maybe we should all take a moment to hang our heads in shame. -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
Richard A Steenbergen wrote:
Does anyone else miss the good old days when nanog readers/attendees knew why pinging the routers you saw in a traceroute directly was not an accurate measurement of anything?
Looking at the Internet Health Check site, I'd think the 50% availability was down to it checking two XO POPs and one of them was totally unavailable. David
participants (3)
-
Berkman, Scott -
David Coulson -
Richard A Steenbergen