[outages] Cogent packet loss ???
Patrick Shoemaker
shoemakerp at vectordatasystems.com
Thu Jul 18 09:28:48 EDT 2013
I'm seeing 30% loss and high latency across a DC-area hop of theirs to Verizon FIOS. This is a routine problem lately but this morning is especially bad.
Apologies for formatting:
My traceroute [v0.83]
sysmon.vectordatasystems.com<http://sysmon.vectordatasystems.com/>(0.0.0.0) Thu Jul 18 09:17:33 2013
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 199.96.110.98 0.0% 311 0.4 0.6 0.3 5.8 0.6
2. v303.riverdale-md-r1.vectordata. 0.0% 311 2.8 0.6 0.3 4.1 0.5
3. v300.calverton-md-r1.vectordata. 0.0% 311 4.2 4.0 3.1 9.3 0.7
4. 205.134.166.229 0.0% 311 10.9 8.4 5.6 25.0 2.2
5. G2-5.MD-117M-RR-DimosNG.ai.net<http://g2-5.md-117m-rr-dimosng.ai.net/> 0.0% 310 8.2 12.6 5.6 209.1 21.5
6. shoki.ai.net<http://shoki.ai.net/> 0.0% 310 17.2 9.7 7.0 22.3 2.3
7. T3-1.DC127KG2MMRC0603.ai.net<http://t3-1.dc127kg2mmrc0603.ai.net/> 0.0% 310 11.0 19.7 5.7 307.1 37.5
8. vl208.mag02.dca01.atlas.cogentco 0.0% 310 12.4 24.4 7.0 239.7 44.1
9. te0-3-0-0.ccr22.dca01.atlas.coge 0.0% 310 9.7 9.7 6.9 24.8 2.4
10. te0-0-0-6.ccr22.ord01.atlas.coge 0.0% 310 27.6 28.6 25.7 43.0 2.5
11. be2003.ccr21.ord03.atlas.cogentc 0.0% 310 26.8 29.1 25.6 44.6 3.1
12. 0.xe-2-3-0.BR3.CHI13.ALTER.NET<http://br3.chi13.alter.net/> 28.7% 310 60.9 104.6 49.5 220.0 46.8
13. ???
14. pool-74-103-38-134.bltmmd.fios.v 27.4% 310 84.4 121.5 67.3 191.2 46.3
Sent from my iPhone
On Jul 18, 2013, at 9:22, "Matthew Huff" <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:
Anyone seeing massive packet loss passing through cogent? Traceroutes appear to be okay, but we are getting a lot of vpn disconnects as well as lost ping packets when we traverse cogent.
1 4 ms 4 ms 5 ms 74.101.107.1
2 4 ms 9 ms 10 ms g1-1-1-5.nycmny-lcr-21.verizon-gni.net<http://g1-1-1-5.nycmny-lcr-21.verizon-gni.net> [130.81.21.150]
3 104 ms 7 ms 7 ms ae0-0.ny325-bb-rtr2.verizon-gni.net<http://ae0-0.ny325-bb-rtr2.verizon-gni.net> [130.81.209.10]
4 19 ms 7 ms 7 ms 0.xe-3-2-0.br2.nyc4.alter.net<http://br2.nyc4.alter.net> [152.63.20.213]
5 * * * Request timed out.
6 68 ms * 53 ms te0-3-0-5.mpd21.jfk02.atlas.cogentco.com<http://jfk02.atlas.cogentco.com> [154.5426.61]
7 145 ms * 56 ms te0-1-0-6.ccr21.jfk04.atlas.cogentco.com<http://jfk04.atlas.cogentco.com> [154.541.162]
8 * 158 ms * 38.104.73.238
9 68 ms * * xe-8-3-0.nycmnyzrj91.lightower.net<http://xe-8-3-0.nycmnyzrj91.lightower.net> [72.22.160.15]
10 123 ms * 136 ms xe-7-2-0.whplnywpj91.lightower.net<http://xe-7-2-0.whplnywpj91.lightower.net> [72.22.160.12]
11 68 ms * 65 ms 162.211.110.2.hvdata.net<http://hvdata.net> [162.211.110.2]
12 * * * Request timed out.
13 57 ms 56 ms * firewall.ox.com<http://firewall.ox.com> [129.77.1.1]
14 160 ms 57 ms * firewall.ox.com<http://firewall.ox.com> [129.77.1.1]
15 71 ms 159 ms 59 ms firewall.ox.com<http://firewall.ox.com> [129.77.1.1]
trace complete.
:\Users\mhuff.MATTHUFF>ping -t 129.77.1.1
C:\Users\mhuff.MATTHUFF>ping -t 129.77.1.1
Pinging 129.77.1.1 with 32 bytes of data:
Reply from 129.77.1.1: bytes=32 time=69ms TTL=251
Reply from 129.77.1.1: bytes=32 time=69ms TTL=251
Reply from 129.77.1.1: bytes=32 time=66ms TTL=251
Request timed out.
Reply from 129.77.1.1: bytes=32 time=68ms TTL=251
Request timed out.
Reply from 129.77.1.1: bytes=32 time=66ms TTL=251
Reply from 129.77.1.1: bytes=32 time=66ms TTL=251
Reply from 129.77.1.1: bytes=32 time=71ms TTL=251
Request timed out.
Request timed out.
Reply from 129.77.1.1: bytes=32 time=68ms TTL=251
Reply from 129.77.1.1: bytes=32 time=68ms TTL=251
Request timed out.
Reply from 129.77.1.1: bytes=32 time=68ms TTL=251
Request timed out.
Request timed out.
Request timed out.
Reply from 129.77.1.1: bytes=32 time=68ms TTL=251
Request timed out.
Request timed out.
Reply from 129.77.1.1: bytes=32 time=141ms TTL=251
Request timed out.
Request timed out.
_______________________________________________
Outages mailing list
Outages at outages.org<mailto:Outages at outages.org>
https://puck.nether.net/mailman/listinfo/outages
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130718/81f1848d/attachment.htm>
More information about the Outages
mailing list