I saw packet loss on Cogent today as well. We have a Boston and NYC site, both saw high latency and some packet loss to almost all destination (even to other Cogent on-net POPs) It seems to have settled down, but I have not gotten a response to support requests. On Wed, Oct 10, 2012 at 6:16 PM, Carlos Alvarez <carlos@televolve.com> wrote:
Unfortunately one of our critical destinations is now advertising a route through Cogent, and they are having some problems it seems. Anyone else?
--- 66.62.162.31 ping statistics --- 62 packets transmitted, 40 received, 35% packet loss, time 61016ms rtt min/avg/max/mdev = 53.803/57.115/62.127/1.730 ms
This is at the same time that latency to the last router before cogent is perfect (1.7-1.9ms).
Relevant route:
3 204.15.220.81 (204.15.220.81) 1.268 ms 1.303 ms 1.289 ms 4 gi3-12.na41.b022559-0.phx02.atlas.cogentco.com (38.122.88.13) 1.497 ms 1.881 ms 1.889 ms 5 vl3810.mag02.phx02.atlas.cogentco.com (66.28.64.209) 12.983 ms 12.979 ms 12.964 ms 6 * te7-4.ccr01.phx02.atlas.cogentco.com (154.54.85.85) 195.832 ms * 7 te0-1-0-7.ccr22.lax01.atlas.cogentco.com (154.54.80.205) 13.472 ms te0-3-0-0.mpd22.lax01.atlas.cogentco.com (154.54.29.25) 12.875 ms te0-1-0-7.ccr22.lax01.atlas.cogentco.com (154.54.80.205) 13.028 ms 8 te3-4.ccr02.lax05.atlas.cogentco.com (154.54.3.10) 151.705 ms te9-8.ccr02.lax05.atlas.cogentco.com (154.54.44.134) 151.715 ms te4-8.ccr02.lax05.atlas.cogentco.com (154.54.30.194) 151.691 ms 9 xe-1-2-1.mpr1.lax12.us.above.net (64.125.13.169) 23.115 ms 23.105 ms 23.090 ms 10 xe-3-0-0.cr1.lax112.us.above.net (64.125.30.17) 13.148 ms 13.090 ms 13.117 ms 11 xe-0-2-0.cr1.sjc2.us.above.net (64.125.26.26) 21.132 ms 21.585 ms 20.958 ms 12 xe-1-0-1.mpr1.den1.us.above.net (64.125.30.133) 50.248 ms 50.045 ms 50.001 ms 13 (208.185.20.58) 50.859 ms 55.178 ms 55.035 ms
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Brent Jones brent@brentrjones.com