[outages] Cogent packet loss ???

[Agle, Jeff]

Cogent has nearly constant peering issues with Alter.Net (Verizon)...although usually I see that in San Jose not NYC.


-----Original Message-----
From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Matthew Huff
Sent: Thursday, July 18, 2013 9:26 AM
To: Matthew Huff; outages at outages.org
Subject: Re: [outages] Cogent packet loss ???

Hmm, we have been having issues for the last 2 hours, took a while to point the issue towards cogent, and 5 minutes after I sent this email, the problem disappeared...


"Once is happenstance, twice is coincidence, three times is enemy action"

-----Original Message-----
From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Matthew Huff
Sent: Thursday, July 18, 2013 9:17 AM
To: outages at outages.org
Subject: [outages] Cogent packet loss ???

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 [130.81.21.150]
 3   104 ms     7 ms     7 ms  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 [152.63.20.213]
 5     *        *        *     Request timed out.
 6    68 ms     *       53 ms  te0-3-0-5.mpd21.jfk02.atlas.cogentco.com [154.5426.61]
 7   145 ms     *       56 ms  te0-1-0-6.ccr21.jfk04.atlas.cogentco.com [154.541.162]
 8     *      158 ms     *     38.104.73.238
 9    68 ms     *        *     xe-8-3-0.nycmnyzrj91.lightower.net [72.22.160.15]
10   123 ms     *      136 ms  xe-7-2-0.whplnywpj91.lightower.net [72.22.160.12]
11    68 ms     *       65 ms  162.211.110.2.hvdata.net [162.211.110.2]
12     *        *        *     Request timed out.
13    57 ms    56 ms     *     firewall.ox.com [129.77.1.1]
14   160 ms    57 ms     *     firewall.ox.com [129.77.1.1]
15    71 ms   159 ms    59 ms  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
https://puck.nether.net/mailman/listinfo/outages

_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages

----------------------------------------------------------------------
CONFIDENTIALITY NOTICE: 
This e-mail transmission may contain confidential information.  This information is solely for the use of the individual(s) or entity to whom or which it was intended.  If not an intended recipient, any review, copying, printing, disclosure, distribution or any other use is strictly prohibited. 
If you have received this email in error, please immediately notify the sender by reply e-mail.  Please delete this e-mail from your files if you are not the intended recipient. Thank you.