Skip to content
Ross's profile

New Member

 • 

2 Messages

Saturday, August 24th, 2013 2:00 PM

Lag spikes for the last month in Chicago

I've been getting multiple lag spikes every hour for the past month. Below is an excerpt of a ping log I took around 3pm 2013/08/24. There are a total of 7 ping spikes within the log but they all look similar, so I'm only including 1 of them. PING google.com (173.194.46.64) 56(84) bytes of data. 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1 ttl=54 time=12.7 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=2 ttl=54 time=15.9 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=3 ttl=54 time=12.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=4 ttl=54 time=11.6 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=5 ttl=54 time=14.4 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=6 ttl=54 time=24.9 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=7 ttl=54 time=11.9 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=8 ttl=54 time=12.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=9 ttl=54 time=11.6 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=10 ttl=54 time=10.7 ms ---------------------- Skip about 1400 lines that look like the above. ---------------------- 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1456 ttl=54 time=12.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1457 ttl=54 time=12.1 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1458 ttl=54 time=2917 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1459 ttl=54 time=1913 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1460 ttl=54 time=906 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1461 ttl=54 time=12.1 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1462 ttl=54 time=12.6 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1463 ttl=54 time=32.1 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1464 ttl=54 time=6068 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1465 ttl=54 time=5179 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1466 ttl=54 time=4172 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1467 ttl=54 time=3164 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1468 ttl=54 time=2156 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1469 ttl=54 time=1148 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1470 ttl=54 time=141 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1471 ttl=54 time=20.3 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1472 ttl=54 time=14.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1474 ttl=54 time=924 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1475 ttl=54 time=13.0 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1476 ttl=54 time=12.1 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1477 ttl=54 time=18.1 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1478 ttl=54 time=4061 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1482 ttl=54 time=3656 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1483 ttl=54 time=16.5 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1484 ttl=54 time=12.3 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1485 ttl=54 time=13.4 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1486 ttl=54 time=13.4 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1487 ttl=54 time=17.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1488 ttl=54 time=12.9 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1489 ttl=54 time=13.0 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1490 ttl=54 time=13.9 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1491 ttl=54 time=15.4 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1492 ttl=54 time=11.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1493 ttl=54 time=19.3 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1494 ttl=54 time=871 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1495 ttl=54 time=998 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1497 ttl=54 time=454 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1498 ttl=54 time=14.1 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1499 ttl=54 time=18.7 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1500 ttl=54 time=14.3 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=1501 ttl=54 time=12.7 ms ------------------------ Skip another 6 lag spikes that look similar to the above till the end. ----------------------- 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=2513 ttl=54 time=12.2 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=2514 ttl=54 time=21.0 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=2515 ttl=54 time=12.0 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=2516 ttl=54 time=17.7 ms 64 bytes from ord08s11-in-f0.1e100.net (173.194.46.64): icmp_req=2517 ttl=54 time=16.0 ms --- google.com ping statistics --- 2517 packets transmitted, 2453 received, 2% packet loss, time 2711 rtt min/avg/max/mdev = 10.196/82.381/7365.657/442.784 ms, pipe 8

Retired Employee

 • 

1.9K Messages

11 years ago

Welcome Ross.  Proper handling of connectivity issues does require assistance from our Local Service Centers.  We can assist in scheduling a service call.  Please let us know.

 

Thank You

New Member

 • 

2 Messages

11 years ago

What would be the best way for me to provide them with the ping-logs I've collected? I doubt the local service center staff are interested in sitting around on the phone with 1 customer for the better part of an hour collecting their own data.