[outages] XO Issues?

[Bill Wichers]

I see the following from Detroit:

---- snip 8< ----
Sfld-XO-Edge>traceroute 206.111.7.222

Type escape sequence to abort.
Tracing the route to 206.111.7.222.ptr.us.xo.net (206.111.7.222)

  1 ge11-0-2d0.mcr1.southfield-mi.us.xo.net (65.46.186.9) [AS 2828] 0 msec 16 ms
ec 0 msec
  2 vb1730.rar3.chicago-il.us.xo.net (216.156.0.185) [AS 2828] 36 msec 36 msec 4
4 msec
  3 ae1d0.cir1.denver2-co.us.xo.net (207.88.13.193) [AS 2828] 32 msec 32 msec 32
msec
  4  *  *  *
  5  *  *  *
  6  *  *  *
  7  *
---- snip 8< ----

   -Bill


From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Ivan Kovacevic
Sent: Tuesday, January 07, 2014 1:38 PM
To: outages at outages.org
Subject: [outages] XO Issues?


Seeing 50% packet loss to 206.111.7.222 from Toronto, Canada


tracert 206.111.7.222
traceroute to 206.111.7.222 (206.111.7.222), 30 hops max, 40 byte packets
1  vlan150-core01.tor1.prioritycolo.com<http://vlan150-core01.tor1.prioritycolo.com> (204.11.49.121)  0.324 ms  0.339 ms  0.427 ms
2  te-1-2.core01.tor1.prioritycolo.com<http://te-1-2.core01.tor1.prioritycolo.com> (204.11.48.132)  0.424 ms  0.558 ms  0.652 ms
3  ix-0-1-3-0.tcore1.TNK-Toronto.as6453.net<http://ix-0-1-3-0.tcore1.TNK-Toronto.as6453.net> (64.86.33.57)  0.188 ms  0.192 ms  0.187 ms
4  if-11-0-0-4.core4.TNK-Toronto.as6453.net<http://if-11-0-0-4.core4.TNK-Toronto.as6453.net> (64.86.33.42)  17.391 ms  17.423 ms  17.463 ms
5  if-0-1-2-0.tcore1.CT8-Chicago.as6453.net<http://if-0-1-2-0.tcore1.CT8-Chicago.as6453.net> (63.243.172.38)  19.250 ms  19.250 ms  19.281 ms
6  p5-1.ir1.chicago2-il.us.xo.net<http://p5-1.ir1.chicago2-il.us.xo.net> (206.111.2.33)  13.928 ms  13.946 ms  13.923 ms
7  207.88.14.193.ptr.us.xo.net<http://207.88.14.193.ptr.us.xo.net> (207.88.14.193)  79.451 ms * 207.88.14.193.ptr.us.xo.net<http://207.88.14.193.ptr.us.xo.net> (207.88.14.193)  78.491 ms
8  * ae1d0.cir1.denver2-co.us.xo.net<http://ae1d0.cir1.denver2-co.us.xo.net> (207.88.13.193)  69.358 ms *
9  206.111.7.222.ptr.us.xo.net<http://206.111.7.222.ptr.us.xo.net> (206.111.7.222)  68.868 ms * *



#ping 206.111.7.222
PING 206.111.7.222 (206.111.7.222) 56(84) bytes of data.
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=2 ttl=61 time=70.0 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=6 ttl=61 time=69.5 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=9 ttl=61 time=69.3 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=10 ttl=61 time=69.7 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=13 ttl=61 time=69.4 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=14 ttl=61 time=108 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=15 ttl=61 time=69.2 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=17 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=18 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=19 ttl=61 time=97.0 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=20 ttl=61 time=98.2 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=21 ttl=61 time=70.5 ms
64 bytes from 206.111.7.222<http://206.111.7.222>: icmp_seq=24 ttl=61 time=69.1 ms

--- 206.111.7.222 ping statistics ---
27 packets transmitted, 13 received, 51% packet loss, time 26014ms
rtt min/avg/max/mdev = 69.151/76.940/108.593/13.574 ms

Best Regards,

Ivan
Star Telecom | www.startelecom.ca<http://www.startelecom.ca/> | SIP Based Services for Contact Centers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20140107/757cf766/attachment.htm>