[outages] Cogent packet loss ???
Clayton Dukes
cdukes at gmail.com
Thu Jul 18 09:38:13 EDT 2013
Hi Matt,
I'm ok coming back to you from my home in NC:
3: ten13-0-0-227.rlghnca-rtr2.nc.rr.com 292.511ms
4: ae19.chrlncpop-rtr1.southeast.rr.com 327.683ms
5: bu-ether24.atlngamq46w-bcr00.tbone.rr.com 374.419ms
6: ae-0-0.pr0.atl20.tbone.rr.com 285.659ms
7: no reply
8: te0-4-0-7.ccr21.atl01.atlas.cogentco.com 363.904ms
9: te0-2-0-3.ccr22.dca01.atlas.cogentco.com 270.264ms asymm 11
10: te0-0-0-14.mpd21.jfk02.atlas.cogentco.com 324.809ms asymm 14
11: te0-6-0-6.ccr21.jfk04.atlas.cogentco.com 319.354ms asymm 15
12: 38.104.73.238 371.430ms
13: xe-8-3-0.nycmnyzrj91.lightower.net 369.340ms
14: xe-7-2-0.whplnywpj91.lightower.net 318.843ms
15: 162.211.110.2.hvdata.net 388.310ms asymm 14
16: no reply
17: no reply
^C
root at cdukes-w530:/var/www/lzpro/tools# ping firewall.ox.com
PING firewall.ox.com (129.77.1.1) 56(84) bytes of data.
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=1 ttl=240 time=284 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=2 ttl=240 time=362 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=3 ttl=240 time=318 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=4 ttl=240 time=369 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=5 ttl=240 time=304 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=6 ttl=240 time=395 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=7 ttl=240 time=281 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=8 ttl=240 time=366 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=9 ttl=240 time=378 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=10 ttl=240 time=335 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=11 ttl=240 time=336 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=12 ttl=240 time=371 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=13 ttl=240 time=308 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=14 ttl=240 time=289 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=15 ttl=240 time=318 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=16 ttl=240 time=358 ms
64 bytes from firewall.ox.com (129.77.1.1): icmp_req=17 ttl=240 time=421 ms
And from Work (Cisco):
C:\Users\cdukes>tracert firewall.ox.com
Tracing route to firewall.ox.com [129.77.1.1]
over a maximum of 30 hops:
1 312 ms 319 ms 392 ms sjce-access-gw1-vla30.cisco.com [10.20.0.94]
2 426 ms 394 ms 382 ms sjce-sbb1-gw1-ten2-3.cisco.com[171.69.14.245]
3 403 ms 449 ms 377 ms sjce-rbb-gw1-ten6-4.cisco.com [171.69.14.33]
4 435 ms 384 ms 428 ms sjce-corp-gw1-gig2-1-0.cisco.com[171.69.7.170]
5 443 ms 449 ms 437 ms sjce-dmzbb-gw1-vla777.cisco.com[128.107.236.38]
6 419 ms 448 ms 428 ms sjck-isp-gw1-ten1-0-0.cisco.com[128.107.239.90]
7 386 ms 410 ms 417 ms sjck-isp-ssw1-ten4-2.cisco.com[128.107.239.222]
8 428 ms 420 ms 419 ms sjce-isp-ssw1-vla851.cisco.com[128.107.239.250]
9 412 ms 414 ms 444 ms sjck-isp-gw1-ten1-1-0.cisco.com[128.107.239.217
]
10 407 ms 468 ms 406 ms TenGigE0-2-0-0.GW5.SCL2.ALTER.NET[152.179.99.15
3]
11 497 ms 528 ms 375 ms 0.xe-4-0-6.XT1.SCL2.ALTER.NET[152.63.50.190]
12 457 ms 437 ms 427 ms 0.xe-4-0-0.BR1.SJC7.ALTER.NET [152.63.51.13]
13 496 ms 427 ms 474 ms 208.178.58.141
14 498 ms 530 ms 531 ms wbs-connect.xe-7-2-1.ar5.jfk1.gblx.net[64.211.1
95.6]
15 599 ms 554 ms 519 ms xe-8-3-0.nycmnyzrj91.lightower.net[72.22.160.15
4]
16 559 ms 506 ms 555 ms xe-7-2-0.whplnywpj91.lightower.net[72.22.160.12
8]
17 541 ms 523 ms 512 ms 162.211.110.2.hvdata.net [162.211.110.2]
18 535 ms 467 ms 452 ms firewall.ox.com [129.77.1.1]
Trace complete.
C:\Users\cdukes>
C:\Users\cdukes>ping firewall.ox.com
Pinging firewall.ox.com [129.77.1.1] with 32 bytes of data:
Reply from 129.77.1.1: bytes=32 time=480ms TTL=235
Reply from 129.77.1.1: bytes=32 time=414ms TTL=235
Reply from 129.77.1.1: bytes=32 time=490ms TTL=235
Reply from 129.77.1.1: bytes=32 time=449ms TTL=235
Ping statistics for 129.77.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 414ms, Maximum = 490ms, Average = 458ms
HTH!
______________________________________________________________
Clayton Dukes
______________________________________________________________
______________________________________________________________
Clayton Dukes
______________________________________________________________
On Thu, Jul 18, 2013 at 9:16 AM, Matthew Huff <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[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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130718/85be4a8b/attachment.htm>
More information about the Outages
mailing list