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 (204.11.49.121) 0.324 ms 0.339 ms 0.427 ms 2 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 (64.86.33.57) 0.188 ms 0.192 ms 0.187 ms 4 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 (63.243.172.38) 19.250 ms 19.250 ms 19.281 ms 6 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 (207.88.14.193) 79.451 ms * 207.88.14.193.ptr.us.xo.net (207.88.14.193) 78.491 ms 8 * ae1d0.cir1.denver2-co.us.xo.net (207.88.13.193) 69.358 ms * 9 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: icmp_seq=2 ttl=61 time=70.0 ms 64 bytes from 206.111.7.222: icmp_seq=6 ttl=61 time=69.5 ms 64 bytes from 206.111.7.222: icmp_seq=9 ttl=61 time=69.3 ms 64 bytes from 206.111.7.222: icmp_seq=10 ttl=61 time=69.7 ms 64 bytes from 206.111.7.222: icmp_seq=13 ttl=61 time=69.4 ms 64 bytes from 206.111.7.222: icmp_seq=14 ttl=61 time=108 ms 64 bytes from 206.111.7.222: icmp_seq=15 ttl=61 time=69.2 ms 64 bytes from 206.111.7.222: icmp_seq=17 ttl=61 time=69.6 ms 64 bytes from 206.111.7.222: icmp_seq=18 ttl=61 time=69.6 ms 64 bytes from 206.111.7.222: icmp_seq=19 ttl=61 time=97.0 ms 64 bytes from 206.111.7.222: icmp_seq=20 ttl=61 time=98.2 ms 64 bytes from 206.111.7.222: icmp_seq=21 ttl=61 time=70.5 ms 64 bytes from 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 | SIP Based Services for Contact Centers
Looks good coming out of Denver through Cogent, except for the packet loss on the last hop: HOST: watcher.axint.net Loss% Snt Last Avg Best Wrst StDev 1. ai-core.axint.net 0.0% 25 0.5 0.6 0.4 1.4 0.2 2. fa0-2.na01.b009854-0.den01.a 0.0% 25 1.0 1.0 0.7 1.6 0.2 3. vl3509.mag02.den01.atlas.cog 0.0% 25 1.3 11.7 0.6 121.3 33.3 4. te0-7-0-5.ccr21.den01.atlas. 0.0% 25 1.6 1.6 0.8 6.0 1.0 5. be2126.ccr21.slc01.atlas.cog 0.0% 25 12.8 12.1 11.6 15.5 0.8 6. be2087.ccr22.sfo01.atlas.cog 0.0% 25 27.3 27.7 27.0 32.5 1.1 7. be2015.ccr21.sjc04.atlas.cog 0.0% 25 28.2 28.3 27.9 29.3 0.3 8. xo.sjc04.atlas.cogentco.com 0.0% 25 27.7 27.8 27.4 29.8 0.5 9. 207.88.13.233.ptr.us.xo.net 0.0% 25 58.4 55.8 54.3 58.4 1.3 10. te-3-0-0.rar3.denver-co.us.x 0.0% 25 55.3 53.9 51.6 55.9 1.6 11. ae0d0.cir1.denver2-co.us.xo. 0.0% 25 48.1 51.7 47.6 96.7 12.6 12. 206.111.7.222.ptr.us.xo.net 44.0% 25 83.2 86.5 83.2 120.2 9.7 Chris On 01/07/2014 11:37 AM, Ivan Kovacevic wrote:
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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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@outages.org] On Behalf Of Ivan Kovacevic Sent: Tuesday, January 07, 2014 1:38 PM To: outages@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
FWIW - We've had reports of VOIP issues (no audio, disconnects) this morning through XO who is our SIP provider. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Bill Wichers Sent: Tuesday, January 07, 2014 12:44 PM To: Ivan Kovacevic; outages@outages.org Subject: Re: [outages] XO Issues? 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@outages.org] On Behalf Of Ivan Kovacevic Sent: Tuesday, January 07, 2014 1:38 PM To: outages@outages.org<mailto:outages@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 The information in this transmittal may be legally privileged, confidential, and/or otherwise protected by law from disclosure, and is intended only for the recipient(s) listed above. If you are neither the intended recipient(s) nor a person responsible for the delivery of this transmittal to the intended recipient(s), you are hereby notified that any distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please notify Agio LLC immediately at (405) 217-3800 or by return e-mail and take the steps necessary to delete it completely from your computer system. Thank you.
Thanks for confirmation, also seeing packetloss over XO from Denver to various destinations. On Tue, Jan 7, 2014 at 11:53 AM, Bunde, Andrew <andrew.bunde@agio.com>wrote:
*FWIW - We've had reports of VOIP issues (no audio, disconnects) this morning through XO who is our SIP provider. *
*From:* Outages [mailto:outages-bounces@outages.org] * On Behalf Of *Bill Wichers *Sent:* Tuesday, January 07, 2014 12:44 PM *To:* Ivan Kovacevic; outages@outages.org *Subject:* Re: [outages] XO Issues?
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@outages.org<outages-bounces@outages.org>] *On Behalf Of *Ivan Kovacevic *Sent:* Tuesday, January 07, 2014 1:38 PM *To:* outages@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 (204.11.49.121) 0.324 ms 0.339 ms 0.427 ms
2 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 (64.86.33.57) 0.188 ms 0.192 ms 0.187 ms
4 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 (63.243.172.38) 19.250 ms 19.250 ms 19.281 ms
6 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 (207.88.14.193) 79.451 ms * 207.88.14.193.ptr.us.xo.net (207.88.14.193) 78.491 ms
8 * ae1d0.cir1.denver2-co.us.xo.net (207.88.13.193) 69.358 ms *
9 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: icmp_seq=2 ttl=61 time=70.0 ms
64 bytes from 206.111.7.222: icmp_seq=6 ttl=61 time=69.5 ms
64 bytes from 206.111.7.222: icmp_seq=9 ttl=61 time=69.3 ms
64 bytes from 206.111.7.222: icmp_seq=10 ttl=61 time=69.7 ms
64 bytes from 206.111.7.222: icmp_seq=13 ttl=61 time=69.4 ms
64 bytes from 206.111.7.222: icmp_seq=14 ttl=61 time=108 ms
64 bytes from 206.111.7.222: icmp_seq=15 ttl=61 time=69.2 ms
64 bytes from 206.111.7.222: icmp_seq=17 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222: icmp_seq=18 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222: icmp_seq=19 ttl=61 time=97.0 ms
64 bytes from 206.111.7.222: icmp_seq=20 ttl=61 time=98.2 ms
64 bytes from 206.111.7.222: icmp_seq=21 ttl=61 time=70.5 ms
64 bytes from 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 | SIP Based Services for Contact Centers
The information in this transmittal may be legally privileged, confidential, and/or otherwise protected by law from disclosure, and is intended only for the recipient(s) listed above. If you are neither the intended recipient(s) nor a person responsible for the delivery of this transmittal to the intended recipient(s), you are hereby notified that any distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please notify Agio LLC immediately at (405) 217-3800 or by return e-mail and take the steps necessary to delete it completely from your computer system. Thank you.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- The information contained in this message is privileged and confidential and protected from disclosure under Title 18 USC 2510-2521. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
Thanks for confirmation, also seeing packetloss over XO from Denver to various destinations. On Tue, Jan 7, 2014 at 12:02 PM, Lucky 225 <Lucky225@2600.com> wrote:
Thanks for confirmation, also seeing packetloss over XO from Denver to various destinations.
On Tue, Jan 7, 2014 at 11:53 AM, Bunde, Andrew <andrew.bunde@agio.com>wrote:
*FWIW - We've had reports of VOIP issues (no audio, disconnects) this morning through XO who is our SIP provider. *
*From:* Outages [mailto:outages-bounces@outages.org] * On Behalf Of *Bill Wichers *Sent:* Tuesday, January 07, 2014 12:44 PM *To:* Ivan Kovacevic; outages@outages.org *Subject:* Re: [outages] XO Issues?
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@outages.org<outages-bounces@outages.org>] *On Behalf Of *Ivan Kovacevic *Sent:* Tuesday, January 07, 2014 1:38 PM *To:* outages@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 (204.11.49.121) 0.324 ms 0.339 ms 0.427 ms
2 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 (64.86.33.57) 0.188 ms 0.192 ms 0.187 ms
4 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 (63.243.172.38) 19.250 ms 19.250 ms 19.281 ms
6 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 (207.88.14.193) 79.451 ms * 207.88.14.193.ptr.us.xo.net (207.88.14.193) 78.491 ms
8 * ae1d0.cir1.denver2-co.us.xo.net (207.88.13.193) 69.358 ms *
9 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: icmp_seq=2 ttl=61 time=70.0 ms
64 bytes from 206.111.7.222: icmp_seq=6 ttl=61 time=69.5 ms
64 bytes from 206.111.7.222: icmp_seq=9 ttl=61 time=69.3 ms
64 bytes from 206.111.7.222: icmp_seq=10 ttl=61 time=69.7 ms
64 bytes from 206.111.7.222: icmp_seq=13 ttl=61 time=69.4 ms
64 bytes from 206.111.7.222: icmp_seq=14 ttl=61 time=108 ms
64 bytes from 206.111.7.222: icmp_seq=15 ttl=61 time=69.2 ms
64 bytes from 206.111.7.222: icmp_seq=17 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222: icmp_seq=18 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222: icmp_seq=19 ttl=61 time=97.0 ms
64 bytes from 206.111.7.222: icmp_seq=20 ttl=61 time=98.2 ms
64 bytes from 206.111.7.222: icmp_seq=21 ttl=61 time=70.5 ms
64 bytes from 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 | SIP Based Services for Contact Centers
The information in this transmittal may be legally privileged, confidential, and/or otherwise protected by law from disclosure, and is intended only for the recipient(s) listed above. If you are neither the intended recipient(s) nor a person responsible for the delivery of this transmittal to the intended recipient(s), you are hereby notified that any distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please notify Agio LLC immediately at (405) 217-3800 or by return e-mail and take the steps necessary to delete it completely from your computer system. Thank you.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- The information contained in this message is privileged and confidential and protected from disclosure under Title 18 USC 2510-2521. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
-- The information contained in this message is privileged and confidential and protected from disclosure under Title 18 USC 2150-2521. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
Thanks for confirmation, also seeing packetloss over XO from Denver to various destinations. On Tue, Jan 7, 2014 at 11:53 AM, Bunde, Andrew <andrew.bunde@agio.com>wrote:
*FWIW - We've had reports of VOIP issues (no audio, disconnects) this morning through XO who is our SIP provider. *
*From:* Outages [mailto:outages-bounces@outages.org] * On Behalf Of *Bill Wichers *Sent:* Tuesday, January 07, 2014 12:44 PM *To:* Ivan Kovacevic; outages@outages.org *Subject:* Re: [outages] XO Issues?
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@outages.org<outages-bounces@outages.org>] *On Behalf Of *Ivan Kovacevic *Sent:* Tuesday, January 07, 2014 1:38 PM *To:* outages@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 (204.11.49.121) 0.324 ms 0.339 ms 0.427 ms
2 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 (64.86.33.57) 0.188 ms 0.192 ms 0.187 ms
4 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 (63.243.172.38) 19.250 ms 19.250 ms 19.281 ms
6 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 (207.88.14.193) 79.451 ms * 207.88.14.193.ptr.us.xo.net (207.88.14.193) 78.491 ms
8 * ae1d0.cir1.denver2-co.us.xo.net (207.88.13.193) 69.358 ms *
9 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: icmp_seq=2 ttl=61 time=70.0 ms
64 bytes from 206.111.7.222: icmp_seq=6 ttl=61 time=69.5 ms
64 bytes from 206.111.7.222: icmp_seq=9 ttl=61 time=69.3 ms
64 bytes from 206.111.7.222: icmp_seq=10 ttl=61 time=69.7 ms
64 bytes from 206.111.7.222: icmp_seq=13 ttl=61 time=69.4 ms
64 bytes from 206.111.7.222: icmp_seq=14 ttl=61 time=108 ms
64 bytes from 206.111.7.222: icmp_seq=15 ttl=61 time=69.2 ms
64 bytes from 206.111.7.222: icmp_seq=17 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222: icmp_seq=18 ttl=61 time=69.6 ms
64 bytes from 206.111.7.222: icmp_seq=19 ttl=61 time=97.0 ms
64 bytes from 206.111.7.222: icmp_seq=20 ttl=61 time=98.2 ms
64 bytes from 206.111.7.222: icmp_seq=21 ttl=61 time=70.5 ms
64 bytes from 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 | SIP Based Services for Contact Centers
The information in this transmittal may be legally privileged, confidential, and/or otherwise protected by law from disclosure, and is intended only for the recipient(s) listed above. If you are neither the intended recipient(s) nor a person responsible for the delivery of this transmittal to the intended recipient(s), you are hereby notified that any distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please notify Agio LLC immediately at (405) 217-3800 or by return e-mail and take the steps necessary to delete it completely from your computer system. Thank you.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- The information contained in this message is privileged and confidential and protected from disclosure under Title 18 USC 2510-2521. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
Not seeing the XO/Denver packet loss any more. Looks like the XO within XO changed for me and the end to end loss is gone. Joseph From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Lucky 225 Sent: Tuesday, January 07, 2014 1:04 PM To: Bunde, Andrew Cc: outages@outages.org Subject: Re: [outages] XO Issues? Thanks for confirmation, also seeing packetloss over XO from Denver to various destinations. On Tue, Jan 7, 2014 at 11:53 AM, Bunde, Andrew <andrew.bunde@agio.com<mailto:andrew.bunde@agio.com>> wrote: FWIW - We've had reports of VOIP issues (no audio, disconnects) this morning through XO who is our SIP provider. From: Outages [mailto:outages-bounces@outages.org<mailto:outages-bounces@outages.org>] On Behalf Of Bill Wichers Sent: Tuesday, January 07, 2014 12:44 PM To: Ivan Kovacevic; outages@outages.org<mailto:outages@outages.org> Subject: Re: [outages] XO Issues? 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<http://206.111.7.222.ptr.us.xo.net> (206.111.7.222) 1 ge11-0-2d0.mcr1.southfield-mi.us.xo.net<http://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<http://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<http://ae1d0.cir1.denver2-co.us.xo.net> (207.88.13.193<tel:%28207.88.13.193>) [AS 2828] 32 msec 32 msec 32 msec 4 * * * 5 * * * 6 * * * 7 * ---- snip 8< ---- -Bill From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Ivan Kovacevic Sent: Tuesday, January 07, 2014 1:38 PM To: outages@outages.org<mailto:outages@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<tel:%28207.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<tel:%28207.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<tel:%28207.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 The information in this transmittal may be legally privileged, confidential, and/or otherwise protected by law from disclosure, and is intended only for the recipient(s) listed above. If you are neither the intended recipient(s) nor a person responsible for the delivery of this transmittal to the intended recipient(s), you are hereby notified that any distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please notify Agio LLC immediately at (405) 217-3800<tel:%28405%29%20217-3800> or by return e-mail and take the steps necessary to delete it completely from your computer system. Thank you. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages -- The information contained in this message is privileged and confidential and protected from disclosure under Title 18 USC 2510-2521. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
participants (7)
-
Bill Wichers -
Bunde, Andrew -
Chris Stone -
Ivan Kovacevic -
Jered Morgan -
Joseph Jackson -
Lucky 225