[outages] Cogent packet loss ???

[Bret Clark]

No, but our path is different

  5. fa0-8.na02.b002148-0.bos01.atlas.cogentco.com 0.0%    87    5.7   
6.4   3.0  45.0   8.2
  6. vl3570.mag01.bos01.atlas.cogentco.com 0.0%    87   15.9  30.8  15.4 
191.5  32.9
  7. te0-4-0-0.ccr22.bos01.atlas.cogentco.com 0.0%    87   17.1  17.9  
14.1 138.9  13.6
  8. 38.104.186.254 1.1%    87   21.3  18.5  13.4 110.0  12.9
  9. xe-1-0-0.nycmnyzrj42.lightower.net 0.0%    87   16.9  27.0  16.9 
106.7  19.7
10. xe-8-3-0.nycmnyzrj91.lightower.net 0.0%    87   43.3  25.1  18.4  
65.4  12.0
11. xe-7-2-0.whplnywpj91.lightower.net 0.0%    87   18.1  24.4  17.7 
208.2  22.3
12. 162.211.110.2.hvdata.net 2.3%    87   19.1  20.8  17.6  79.8   7.6
13. firewall.ox.com 0.0%    87   20.8  22.6  17.9  77.5   9.3


On 07/18/2013 09:16 AM, Matthew Huff 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 [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