Reply
Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Intermittent lag / high ping - traced to a Comcast core router, verified by ping

[ Edited ]

I'm obviously not the only one with this issue.  Here is the e-mail I've sent to we_can_help and comcast_cares:
============
A service technician came today and verified that my cable modem and home systems are operating perfectly.  The service worked fine for a few hours after he left, and then just now I've had a 5 minute outage (no service, line disconnected for 5 mins) then again a disconnect of IP transport for 30 seconds.
 
I fully expect that I will continue to see long latency delays in your core router, as I've documented in previous e-mails being traceable directly to one of Comcast's core routers named "pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net."
 
Please connect me with a support engineer (US based, connected to the edge and core router services) so that this problem can be fixed.
 
- L
 
Below are the previous ping and traceroute records from these periodic Comcast core router outages
 
From: XXXXXXXXXXXXXX
Date: Friday, July 19, 2013 8:38 PM
To:, Shelly" <SHELLY>, Comcast Customer Support <COMCAST_CUSTOMERSUPPORT>, <WE_CAN_HELP>
Subject:&nbsp;Re: Comcast Escalation ESL00996618 - XXXXXXXXXXXXXX - 8155200330283880
&nbsp;


Hello,
&nbsp;
It is not acceptable in my opinion to have these outages go substantially unanswered by the customer support team. &nbsp;In other words: this outage requires that a technical team with sufficient experience answer the substance of the complaint, and not only answer to the issue of poor customer service overall. &nbsp;This problem is intermittent and recurring, and should be addressed, which will require a backend technical escalation. &nbsp;The field service call scheduled for tomorrow morning&nbsp;will not address the issue with Comcast's service.
&nbsp;
The substance of the problem is as follows:
It appears that Comcast has a problem is with a Comcast router named "pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net". &nbsp;Tonight, that router appears to be working correctly. &nbsp;However, it was NOT working correctly yesterday&nbsp;(see traceroute and ping results below)&nbsp;and during periods last week when our service was interrupted as proven by those traceroute results I provided previously.
&nbsp;
I expect that based on this evidence, a technical escalation will be performed and someone from Comcast will answer to the actual technical outage in a manner sufficient to address the root cause of this.&nbsp;
&nbsp;
- L
&nbsp;
From:&nbsp;" Shelly" <SHELLY>
Date:&nbsp;Friday, July 19, 2013 5:24 PM
To:&nbsp;XXXXXX <XXXX>
Subject:&nbsp;Comcast Escalation ESL00996618 - XXXXXXXXXXXXX - 8155200330283880
&nbsp;



Good evening,
&nbsp;
The Comcast Executive Customer Relations department has received your concern, via our Digital Media Team. We greatly appreciate the time you have taken to bring this situation to our attention.
&nbsp;
At this time, you are scheduled for a service call on tomorrow, 07/20/13 with an arrival timeframe of 0800-1000A.&nbsp; A technician will be there to further investigate and troubleshoot/resolve your reported issues with service.&nbsp; For your time and frustration, I have applied a onetime credit to your account in the amount of $20.00 which will approve overnight tonight and be present on your next monthly statement.&nbsp; Should you have additional questions please feel free to contact us again.
&nbsp;
Thank you,
&nbsp;
Shelly Williamson
Comcast - Executive Customer Relations

Original Message Follows: ------------------------&nbsp;

&nbsp;


Hi,
&nbsp;
The problem I'm having is intermittent delays in my internet service (every 60 seconds or so).
&nbsp;
I have called the support lines (in the Philippines) and they have not been helpful at all. &nbsp;I have also used the online chat service to no affect. &nbsp;This requires a technician with experience with networks, not an outsourced person reading a script.
&nbsp;
Please help – this is an ugly scar on Comcast's service record so far.
&nbsp;
Here is a ping to the Google service clearly showing the problem:
&nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=595 ttl=55 time=15.7 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=596 ttl=55 time=15.3 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=597 ttl=55 time=15.6 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=598 ttl=55 time=15.3 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=599 ttl=55 time=15.6 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=602 ttl=55 time=7733 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=604 ttl=55 time=5734 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=605 ttl=55 time=4734 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=606 ttl=55 time=3734 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=603 ttl=55 time=6734 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=607 ttl=55 time=2734 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=608 ttl=55 time=1734 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=610 ttl=55 time=213 ms
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=611 ttl=55 time=28.8 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=612 ttl=55 time=13.5 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=613 ttl=55 time=31.0 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;
64 bytes from nuq05s01-in-f18.1e100.net (74.125.239.114): icmp_seq=614 ttl=55 time=15.2 ms&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;

^C
--- www.google.com ping statistics ---
639 packets transmitted, 630 received, 1% packet loss, time 638915ms
rtt min/avg/max/mdev = 13.209/118.160/7733.105/647.186 ms, pipe 8
&nbsp;
Also a traceroute:
&nbsp;

[root@gpumonster ~]# traceroute www.google.com
traceroute to www.google.com (74.125.239.52), 30 hops max, 60 byte packets
&nbsp;1 &nbsp;192.168.1.1 (192.168.1.1) &nbsp;0.318 ms &nbsp;0.371 ms &nbsp;0.287 ms
&nbsp;2 &nbsp;c-98-207-16-1.hsd1.ca.comcast.net (98.207.16.1) &nbsp;17.529 ms &nbsp;16.374 ms &nbsp;31.881 ms
&nbsp;3 &nbsp;te-7-1-ur01.sanmateo.ca.sfba.comcast.net (68.87.197.105) &nbsp;17.334 ms &nbsp;17.297 ms &nbsp;17.390 ms
&nbsp;4 &nbsp;te-0-1-0-2-ar01.sfsutro.ca.sfba.comcast.net (68.87.192.230) &nbsp;20.044 ms &nbsp;20.983 ms &nbsp;21.095 ms
&nbsp;5 &nbsp;* * he-3-9-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.91.45) &nbsp;22.174 ms
&nbsp;6 &nbsp;pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net (68.86.87.146) &nbsp;21.958 ms &nbsp;21.338 ms &nbsp;21.375 ms
&nbsp;7 &nbsp;* * *
&nbsp;8 &nbsp;72.14.232.136 (72.14.232.136) &nbsp;18.324 ms &nbsp;18.451 ms &nbsp;17.883 ms
&nbsp;9 &nbsp;72.14.232.35 (72.14.232.35) &nbsp;15.677 ms &nbsp;13.662 ms &nbsp;14.694 ms
10 &nbsp;nuq04s19-in-f20.1e100.net (74.125.239.52) &nbsp;19.122 ms &nbsp;18.009 ms &nbsp;18.902 ms
&nbsp;
- L</XXXX></SHELLY>

New Visitor
Backwardx
Posts: 2
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

You are not alone, I've done a pathping and traced it to comcast servers.  I have spent countless hours on the phone.  Technician schedule on Monday... I'm sure he'll change cables or something.  I just swapped out a modem, at Comcast behest.  I wish they would acknowledge this and fix it.  I do not want credit, I want a working internet. 

 

Packet losses verified by pathping:

 

Tracing route to 12.129.209.68 over a maximum of 30 hops

  0  Matt-PC.hsd1.pa.comcast.net. [192.168.1.110]   1  192.168.1.1   2  174.55.144.1   3     *     te-0-0-0-2-sur01.york.pa.pitt.comcast.net [68.85.43.225]   4  te-0-12-0-2-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.57]   5  be-2-ar03.pittsburgh.pa.pitt.comcast.net [68.85.75.125]   6  he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]   7  pos-1-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]   8     *        *     192.205.37.33   9     *     cr1.n54ny.ip.att.net [12.122.131.86]  10  cr2.cgcil.ip.att.net [12.122.1.2]  11     *        *     cr1.cgcil.ip.att.net [12.122.2.53]  12  cr2.dvmco.ip.att.net [12.122.31.85]  13  cr1.slkut.ip.att.net [12.122.30.25]  14     *        *        *     Computing statistics for 325 seconds...             Source to Here   This Node/Link Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address   0                                           Matt-PC.hsd1.pa.comcast.net. [192.168.1.110]                                 0/ 100 =  0%   |   1    3ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1                                42/ 100 = 42%   |   2  968ms    53/ 100 = 53%    11/ 100 = 11%  174.55.144.1                                 0/ 100 =  0%   |   3  771ms    42/ 100 = 42%     0/ 100 =  0%  te-0-0-0-2-sur01.york.pa.pitt.comcast.net [68.85.43.225]                                 0/ 100 =  0%   |   4 1092ms    46/ 100 = 46%     4/ 100 =  4%  te-0-12-0-2-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.57]                                 0/ 100 =  0%   |   5 1011ms    42/ 100 = 42%     0/ 100 =  0%  be-2-ar03.pittsburgh.pa.pitt.comcast.net [68.85.75.125]                                 4/ 100 =  4%   |   6  901ms    47/ 100 = 47%     1/ 100 =  1%  he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]                                 0/ 100 =  0%   |   7  848ms    46/ 100 = 46%     0/ 100 =  0%  pos-1-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]                                13/ 100 = 13%   |   8  918ms    59/ 100 = 59%     0/ 100 =  0%  192.205.37.33                                41/ 100 = 41%   |   9  ---     100/ 100 =100%     0/ 100 =  0%  cr1.n54ny.ip.att.net [12.122.131.86]                                 0/ 100 =  0%   |  10  ---     100/ 100 =100%     0/ 100 =  0%  cr2.cgcil.ip.att.net [12.122.1.2]                                 0/ 100 =  0%   |  11  ---     100/ 100 =100%     0/ 100 =  0%  cr1.cgcil.ip.att.net [12.122.2.53]                                 0/ 100 =  0%   |  12  ---     100/ 100 =100%     0/ 100 =  0%  cr2.dvmco.ip.att.net [12.122.31.85]                                 0/ 100 =  0%   |  13  ---     100/ 100 =100%     0/ 100 =  0%  cr1.slkut.ip.att.net [12.122.30.25]

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Yes - I've read yours and others' numerous posts about related issues.  I've also had a decade of experience with Comcast having internal issues that have required literally hundreds of hours of my time on the telephone until I could reach the one person who forwarded me to someone with access to the internal network operations support.

 

One would think that Comcast should value experienced customers pointing out issues in detail with their services. Unless perhaps this is a known issue to them - perhaps some kind of new QoS designed to penalize gamers?  More likely it's just a known issue with overloaded core routers.

 

At any rate - this forum thread is just another step toward the expected outcome: after another 50-100 hours of my time over the next few weeks I will eventually be introduced to someone who can interface with the internal network operations team.  At that point, they will fix something, and things will be fine for my house for another 12-18 mos at which time I'll have to do this again.

New Visitor
TiZiK
Posts: 1
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

i'm happy to see that there are gamers out there like me, who have noticed the BS comcast is handing us. people who have experience and knowledge that its comcast servers at fault. i recently had my modem swaped after having spikes and packet loss and being kicked from online games and after weeks of trouble shooting the problem magically resolved. its back again a tech is supossed to be out on Tuesday... lets see what they say

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

And just now I had three events of 7-10 second lags of Netflix, which correlate perfectly with a log of ping times I have continuously running to a google server.

 

So, again, I have conclusive evidence that Comcast is dropping packets in their router network.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I just experienced ten minutes of network packet drops and lags, starting at about 8:40PM PST.  I noticed it when my Netflix program stuttered and reloaded.
 
Since I've been having problems with the Comcast service, I have been running a continuous log of ping times to a google server.  When the Netflix program stuttered, the timing correlated perfectly with dropped packets and ping delays to the google server.
 
I have attached the log of pings that I had running during these events.
 
This is very clear evidence that a Comcast system is malfunctioning sporadically (mostly at night).  I will also post this to the public Comcast forum.
 
Escalate this to a network engineer now please.

 

========================

Pings to Google during outage

========================

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3405 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3406 ttl=55 time=17.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3407 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3408 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3409 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3410 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3411 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3412 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3413 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3414 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3415 ttl=55 time=32.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3416 ttl=55 time=16.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3417 ttl=55 time=16.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3418 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3419 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3420 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3421 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3422 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3423 ttl=55 time=15.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3424 ttl=55 time=16.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3425 ttl=55 time=17.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3426 ttl=55 time=16.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3427 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3428 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3429 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3430 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3431 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3432 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3433 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3434 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3435 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3436 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3437 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3438 ttl=55 time=13.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3439 ttl=55 time=4593 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3440 ttl=55 time=3593 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3442 ttl=55 time=1593 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3441 ttl=55 time=2593 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3443 ttl=55 time=593 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3444 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3445 ttl=55 time=17.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3446 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3447 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3448 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3449 ttl=55 time=21.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3450 ttl=55 time=23.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3451 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3452 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3453 ttl=55 time=14.6 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3454 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3455 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3456 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3457 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3458 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3459 ttl=55 time=20.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3460 ttl=55 time=17.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3461 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3462 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3464 ttl=55 time=13.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3465 ttl=55 time=17.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3466 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3467 ttl=55 time=1022 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3468 ttl=55 time=23.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3469 ttl=55 time=22.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3470 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3471 ttl=55 time=30.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3472 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3473 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3474 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3475 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3476 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3477 ttl=55 time=17.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3478 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3479 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3480 ttl=55 time=944 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3483 ttl=55 time=1796 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3484 ttl=55 time=893 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3486 ttl=55 time=40.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3487 ttl=55 time=17.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3488 ttl=55 time=893 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3489 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3490 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3491 ttl=55 time=23.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3492 ttl=55 time=835 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3493 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3495 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3496 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3497 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3498 ttl=55 time=21.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3499 ttl=55 time=18.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3500 ttl=55 time=17.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3501 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3502 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3503 ttl=55 time=16.2 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3504 ttl=55 time=29.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3505 ttl=55 time=13.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3506 ttl=55 time=13.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3507 ttl=55 time=44.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3508 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3509 ttl=55 time=218 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3510 ttl=55 time=7267 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3511 ttl=55 time=6269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3512 ttl=55 time=5269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3513 ttl=55 time=4269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3514 ttl=55 time=3269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3515 ttl=55 time=2269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3516 ttl=55 time=1269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3517 ttl=55 time=269 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3518 ttl=55 time=68.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3519 ttl=55 time=53.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3520 ttl=55 time=15.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3521 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3522 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3523 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3524 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3525 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3526 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3527 ttl=55 time=16.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3528 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3529 ttl=55 time=20.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3530 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3531 ttl=55 time=30.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3532 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3533 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3534 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3535 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3536 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3537 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3538 ttl=55 time=49.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3539 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3540 ttl=55 time=33.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3541 ttl=55 time=13.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3542 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3543 ttl=55 time=76.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3544 ttl=55 time=19.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3545 ttl=55 time=21.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3546 ttl=55 time=18.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3547 ttl=55 time=20.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3548 ttl=55 time=16.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3549 ttl=55 time=7910 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3550 ttl=55 time=6911 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3551 ttl=55 time=5911 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3553 ttl=55 time=3911 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3552 ttl=55 time=4911 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3554 ttl=55 time=2911 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3556 ttl=55 time=911 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3555 ttl=55 time=1911 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3557 ttl=55 time=22.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3558 ttl=55 time=33.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3559 ttl=55 time=65.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3560 ttl=55 time=22.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3561 ttl=55 time=15.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3562 ttl=55 time=17.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3563 ttl=55 time=17.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3564 ttl=55 time=24.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3565 ttl=55 time=17.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3567 ttl=55 time=16.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3568 ttl=55 time=16.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3569 ttl=55 time=13.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3570 ttl=55 time=28.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3571 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3572 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3573 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3574 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3575 ttl=55 time=18.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3576 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3577 ttl=55 time=20.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3578 ttl=55 time=16.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3579 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3580 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3581 ttl=55 time=21.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3582 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3583 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3584 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3585 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3586 ttl=55 time=34.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3587 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3588 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3589 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3590 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3591 ttl=55 time=19.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3592 ttl=55 time=16.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3593 ttl=55 time=17.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3594 ttl=55 time=16.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3595 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3596 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3597 ttl=55 time=17.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3598 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3599 ttl=55 time=15.5 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3600 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3601 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3602 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3603 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3604 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3605 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3606 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3607 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3608 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3609 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3610 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3611 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3612 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3613 ttl=55 time=21.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3614 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3615 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3616 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3617 ttl=55 time=35.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3618 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3619 ttl=55 time=18.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3620 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3621 ttl=55 time=18.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3622 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3623 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3624 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3625 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3626 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3627 ttl=55 time=17.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3628 ttl=55 time=19.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3629 ttl=55 time=19.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3630 ttl=55 time=17.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3631 ttl=55 time=31.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3632 ttl=55 time=16.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3633 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3634 ttl=55 time=16.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3635 ttl=55 time=18.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3636 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3637 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3638 ttl=55 time=17.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3639 ttl=55 time=31.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3640 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3641 ttl=55 time=18.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3642 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3643 ttl=55 time=16.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3644 ttl=55 time=34.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3645 ttl=55 time=17.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3646 ttl=55 time=14.9 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3647 ttl=55 time=20.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3648 ttl=55 time=13.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3649 ttl=55 time=44.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3650 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3651 ttl=55 time=22.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3652 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3653 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3654 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3655 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3656 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3657 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3658 ttl=55 time=29.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3659 ttl=55 time=34.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3660 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3661 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3662 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3663 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3664 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3665 ttl=55 time=21.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3666 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3667 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3668 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3669 ttl=55 time=15.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3670 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3671 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3672 ttl=55 time=19.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3673 ttl=55 time=20.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3674 ttl=55 time=16.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3675 ttl=55 time=29.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3676 ttl=55 time=16.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3677 ttl=55 time=16.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3678 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3679 ttl=55 time=17.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3680 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3681 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3682 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3683 ttl=55 time=17.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3684 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3685 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3686 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3687 ttl=55 time=22.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3688 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3689 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3690 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3691 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3692 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3693 ttl=55 time=16.0 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3694 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3695 ttl=55 time=17.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3696 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3697 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3698 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3699 ttl=55 time=21.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3700 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3701 ttl=55 time=16.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3702 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3703 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3704 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3705 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3706 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3707 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3708 ttl=55 time=17.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3709 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3710 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3711 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3712 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3713 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3714 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3715 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3716 ttl=55 time=23.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3717 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3718 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3719 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3720 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3721 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3722 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3723 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3724 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3725 ttl=55 time=31.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3726 ttl=55 time=20.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3727 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3728 ttl=55 time=33.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3729 ttl=55 time=17.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3730 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3731 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3732 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3733 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3734 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3735 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3736 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3737 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3738 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3739 ttl=55 time=22.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3740 ttl=55 time=15.8 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3741 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3742 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3743 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3744 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3745 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3746 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3747 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3748 ttl=55 time=14.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3749 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3750 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3751 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3752 ttl=55 time=19.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3753 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3754 ttl=55 time=16.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3755 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3756 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3757 ttl=55 time=16.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3758 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3759 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3760 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3761 ttl=55 time=21.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3762 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3763 ttl=55 time=30.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3764 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3764 ttl=55 time=602 ms (DUP!)
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3765 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3766 ttl=55 time=19.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3767 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3768 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3769 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3770 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3771 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3772 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3773 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3774 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3775 ttl=55 time=3027 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3776 ttl=55 time=2028 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3777 ttl=55 time=1028 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3778 ttl=55 time=28.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3779 ttl=55 time=25.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3780 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3781 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3782 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3783 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3784 ttl=55 time=16.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3785 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3786 ttl=55 time=16.4 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3787 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3788 ttl=55 time=16.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3789 ttl=55 time=16.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3790 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3791 ttl=55 time=13.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3792 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3793 ttl=55 time=17.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3794 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3795 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3796 ttl=55 time=16.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3797 ttl=55 time=5012 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3798 ttl=55 time=4013 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3801 ttl=55 time=1014 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3799 ttl=55 time=3014 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3800 ttl=55 time=2014 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3802 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3803 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3804 ttl=55 time=13.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3805 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3806 ttl=55 time=15.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3807 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3808 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3809 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3810 ttl=55 time=17.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3811 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3812 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3813 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3814 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3815 ttl=55 time=17.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3816 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3817 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3818 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3819 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3820 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3821 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3822 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3823 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3824 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3825 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3826 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3827 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3828 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3829 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3830 ttl=55 time=30.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3831 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3832 ttl=55 time=16.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3833 ttl=55 time=16.4 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3834 ttl=55 time=16.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3835 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3836 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3837 ttl=55 time=16.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3838 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3839 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3840 ttl=55 time=20.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3841 ttl=55 time=14.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3842 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3843 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3844 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3845 ttl=55 time=14.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3846 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3847 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3848 ttl=55 time=29.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3849 ttl=55 time=13.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3850 ttl=55 time=16.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3851 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3852 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3853 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3854 ttl=55 time=48.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3855 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3856 ttl=55 time=18.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3857 ttl=55 time=16.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3858 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3859 ttl=55 time=17.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3860 ttl=55 time=29.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3861 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3862 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3863 ttl=55 time=254 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3864 ttl=55 time=17.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3865 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3866 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3867 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3868 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3869 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3870 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3871 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3872 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3873 ttl=55 time=16.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3874 ttl=55 time=16.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3875 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3876 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3877 ttl=55 time=26.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3878 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3879 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3880 ttl=55 time=13.9 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3881 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3882 ttl=55 time=15.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3883 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3884 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3886 ttl=55 time=15.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3887 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3888 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3889 ttl=55 time=21.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3890 ttl=55 time=14.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3891 ttl=55 time=23.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3892 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3893 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3894 ttl=55 time=19.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3895 ttl=55 time=15.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3896 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3897 ttl=55 time=13.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3898 ttl=55 time=13.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3899 ttl=55 time=16.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3900 ttl=55 time=13.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3901 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3902 ttl=55 time=16.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3903 ttl=55 time=23.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3904 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3905 ttl=55 time=13.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3906 ttl=55 time=13.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3907 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3908 ttl=55 time=14.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3909 ttl=55 time=14.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3910 ttl=55 time=14.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3911 ttl=55 time=15.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3912 ttl=55 time=13.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3913 ttl=55 time=31.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3914 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3915 ttl=55 time=30.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3916 ttl=55 time=15.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3917 ttl=55 time=17.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3918 ttl=55 time=28.7 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3919 ttl=55 time=14.5 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3920 ttl=55 time=14.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3921 ttl=55 time=16.9 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3922 ttl=55 time=32.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3923 ttl=55 time=14.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3924 ttl=55 time=30.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3925 ttl=55 time=15.6 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3926 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3927 ttl=55 time=15.4 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3928 ttl=55 time=17.1 ms

64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3929 ttl=55 time=32.1 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3930 ttl=55 time=20.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3931 ttl=55 time=21.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3932 ttl=55 time=15.0 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3933 ttl=55 time=15.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3934 ttl=55 time=28.8 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3935 ttl=55 time=29.2 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3936 ttl=55 time=29.3 ms
64 bytes from nuq05s02-in-f17.1e100.net (74.125.239.145): icmp_seq=3937 ttl=55 time=14.7 ms

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Here is a plot of the ping times during the Comcast outage:

 

Plot

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

And here is one more plot – I stopped using Netflix at 10:10PM – note that the packet loss and high ping continues to happen.  There is no other internet activity from the house at this time, but the delays are still occurring.

 

At this point it should be obvious to anyone trained in network engineering that this is a problem with the Comcast network.

 

Please assign a network engineer from the backend support team to trace this down.

 

Plot

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

The outage continues – here's a plot on a logarithmic scale so you can see all of the response times.

 

To summarize: starting at 8:40PM tonight, some network event happened in the Comcast network that caused my house to lose reliable internet connectivity.  This is the same behavior we have been experiencing for several weeks now.  At night, we lose reliable internet connectivity.  In the mornings, we return to normal internet connectivity.

 

The data presented below, combined with a thorough validation of my cable modem, line and home equipment by a field technician, proves that this problem is due to Comcast's network malfunctioning. 

 

At this time Comcast should escalate this problem to a qualified network operations engineer to resolve the problem with the Comcast Internet services in my neighborhood.

 

Log Scale Plot to 10:52PM

Visitor
Posts: 3
Registered: ‎01-27-2010

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I'm an online gamer and for the last month the sites i've used would ping 55 to 80, now lately over 600. During online chat I was asked to do speedtest.net .. It varied between 32 down 4 up  to 7 down .3 up. The chat person said she saw nothing wrong on her end. Obiously she is either a novice or they cannot tell the quality of service only if you got it or not. I told her to send a tech, OR I'll call the main office want a rebate and have them pull their equiptment out. We spend $226.00 a month for tv and internet and I will not put up with sub-par service.

 

New Visitor
Kezel
Posts: 1
Registered: ‎07-21-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Same here, I haven't been getting such drastic pings (in the thousands) but gaming is impossible.

 

I'll ping or tracert to google or yahoo.com and I'm seeing a similar spread of numbers, except mine bounces up to the 200-400 range, rather than 4,000.  The bouncing up and down really screws with the gaming.

 

I've tried a new modem, bypassing my modem etc.

 

There's nothing on my end that's wrong.  My brother is also having an extremely similar issue.  He lives about 50 miles away.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

The end of the outage was at 5:40AM this morning, as can be seen clearly in the below plot of ping times to Google.

 

What is interesting is that this Comcast outage appears to be exactly eight hours long.  Perhaps this corresponds to a scheduled QoS setting on the router, designed to be active during the night time hours?  This schedule has been similar for the last few weeks.

 

Log Plot of Ping to Google over 12 hours

 

Comcast should assign a network engineer with access to backend systems to fix this outage. 

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I am on chat with a support person in Cebu, Phillipines who after checking on the escalation has found that Comcast will send a Level 2 technician to play with my line again.  Those reading this thread who have an understanding of networks will realize that Comcast is not doing the correct thing by sending a technician to troubleshoot my line or modem again.  The problem is clearly inside the Comcast network equipment, as evidenced by the ping traces over time.

 

So it should also be obvious to those reading this thread that Comcast is wasting even more of my time in this process by executing redundant and irrelevant support.

 

Here is the end of my chat transcript:

 

Louhtes Gayle: It is a level 2 tech visit , I believe the appointment yesterday was for repair technician. Level 2 tech are able to reposition your connection in the pole .

L: As pointed out many times - it is a waste of time to look at my line and local equipment (cable modem, etc)

L: reposition my connection on the pole? This problem does not relate to my line.

L: If this were being handled by the correct dept, they would read the posting here:

L: http://forums.comcast.com/t5/Basic-Internet-Connectivity-And/Intermittent-lag-high-ping-traced-to-a-...

L: and after reading it, they would stop trying to troubleshoot my line because it is now obvious that the problem is inside the Comcast equipment

L: I would like to have this information added to the escalation ticket - they need to escalate to level 3

Louhtes Gayle: I want to let you know that we have a process , we trouble shoot any issues remotely then send technician to determine the cause .The most we can do is to create an escalation ticket and to set up and appointment which is what the previous rep did . We at the moment needs to wait for the feedback .

Louhtes Gayle: Certainly I will update the escalation ticket now with link you have provided and will include our transcript for reference

L: Thank you

 

Regular Contributor
ArberA
Posts: 30
Registered: ‎06-13-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

[ Edited ]

I to am having problems between certain time frames for the past 8 weeks now and have had 5 techs come out to my home and have repeatly asked to speak with a network engineer or a network backbone manger to no luck. i supposedly will finally have a superviser/manager coming out this week to check on my situation but im not holding my breath on that one. as you can see from the thread i have started my signal and line is fine and has been verified by 5 techs now that its not a line problem... i am also located in chicago so this seems like a giant nation wide problems. my problems seem to happen 5am-10am CST and 7/8pm-midnight CST.... i am keeping my thread updated and will be following your thread in hopes for a solution...

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

This morning I received this from the local tech supervisor.
==========
 
From: "XXXXXX, Jorge" <Jorge_XXXXXXX@cable.comcast.com>
Date: Sunday, July 21, 2013 9:00 AM
Subject: Re: Escalation needed - third attempt - 15 hours on phone so far
 
Good morning L,
I'm currently off until this coming Wednesday and there is no level 2 tech, the tech who was out at your location yesterday should of escalated a Network ticket to our Network Department. I do understand your frustration with our service and tomorrow I'll be reaching out to our Network team and submit the ticket myself and I'll be circling back with the Network Supervisor as well. Once I get some resolution on your issue I'll e-mail you the information, also thanks again for the DATA this helps out a lot. 
 
Jorge XXXXXXX  
Contributor
Posts: 6
Registered: ‎09-29-2008

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I'm located in Illinois and have been experiencing extremely slow connection speeds since 7/18. The connection seems to be intermittently dropping for a few seconds at a time and I believe you have good documentation about what's going on.

 

I've been hesitant to report this to Comcast since I know from past experience they'll try to send a tech to search for a problem on my end. I've periodically dealt with this same issue over many years and the problem has *never* been on my end.

Contributor
christian2150
Posts: 9
Registered: ‎06-10-2012

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

lag/high ping in Northbrook, Illinois as well...

 

it is NOT on my end either.

Regular Contributor
ArberA
Posts: 30
Registered: ‎06-13-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

B_ark and christian.. are you noticing this at certain time frames or just randomly.. i would be interested to see your traceroutes to google.com and see if we all go thru the same comcast routers since we are live in the chicagoland area....

Contributor
christian2150
Posts: 9
Registered: ‎06-10-2012

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

this happened a couple of months ago where me and my friends (same neighbhorhood, different homes) had this same issue of lag spikes. I called Comcast a bunch of times and they kept refusing that its on their side when it clearly was. it just went away after they mass restarted everyones signal in my area.

Contributor
christian2150
Posts: 9
Registered: ‎06-10-2012

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

173.194.46.14 is from United States(US) in region North America

TraceRoute from Network-Tools.com to 173.194.46.14 [google.com]
Hop	(ms)	(ms)	(ms)		     IP Address	Host name
1 	  0 	  0 	  0 	     8.9.232.73	  xe-5-3-0.edge3.dallas1.level3.net  
2 	  0 	  0 	  0 	     4.69.145.12	  ae-1-60.edge2.dallas3.level3.net  
3 	  0 	  0 	  0 	     4.68.70.166	   -  
4 	  Timed out 	  0 	  0 	     72.14.233.67	   -  
5 	  10 	  0 	  0 	     209.85.240.79	   -  
6 	  0 	  0 	  0 	     173.194.46.14	  dfw06s27-in-f14.1e100.net  
Trace complete

 

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

There was another lag / packet drop event in the middle of the day, but otherwise the day has been relatively free of Comcast outage behavior as seen in the 19 hour ping trace plot:

 

19 hours of ping to Google

 

Tonight after 8:30 PM or so I expect we will see the full outage behavior again.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

The problem (increased lag times) just started again promptly at 8:40PM, same as last night.

 

Comcast - you need to get a network engineer to diagnose this problem now.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Here is the plot of high ping times showing that the problem has started again, promptly at 8:40 like last night (and the last several weeks):

 

Plot of ping times to Google

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

And here is a traceroute to the google server during tonight's outage:

 

traceroute to www.google.com (74.125.239.49), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.365 ms 0.402 ms 0.303 ms
2 c-98-207-16-1.hsd1.ca.comcast.net (98.207.16.1) 31.792 ms 32.931 ms 34.794 ms
3 te-7-1-ur01.sanmateo.ca.sfba.comcast.net (68.87.197.105) 19.671 ms 19.748 ms 19.730 ms
4 te-0-1-0-4-ar01.sfsutro.ca.sfba.comcast.net (68.85.154.106) 24.882 ms 24.996 ms 24.979 ms
5 he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.157) 25.033 ms * *
6 pos-0-3-0-0-pe01.529bryant.ca.ibone.comcast.net (68.86.87.142) 23.745 ms 24.006 ms 23.937 ms
7 * * *
8 72.14.232.136 (72.14.232.136) 22.582 ms 18.466 ms 17.304 ms
9 72.14.232.35 (72.14.232.35) 17.207 ms 17.388 ms 17.319 ms
10 nuq04s19-in-f17.1e100.net (74.125.239.49) 16.077 ms 17.251 ms 16.190 ms

 

Again - we see packets dropping inside the Comcast network.

 

Come on Comcast - answer the mail here...

Regular Contributor
ArberA
Posts: 30
Registered: ‎06-13-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

so this morning the speeds lags happened again but during the usual timeframe during a smaller time frame then normal but still happened for about an hour.. here are screen captures of trace routes to google and ping test.. can you take a look since looking at these is not my specialty.

 

Trace routes:

http://s23.postimg.org/ah79n32aj/tracertwhen_BAD1.jpg

http://s24.postimg.org/bjalqtqh1/tracertwhen_BAD2.jpg

http://s21.postimg.org/wbu6cslcn/tracertwhen_BAD3.jpg

 

Ping tests:

http://s22.postimg.org/5esa4zku9/pingtestswhenbad.jpg

 

 

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

This plot shows two nights of packet loss and ping times as high as 14 seconds, each time between the hours of 8:40PM and 5AM.  It is clear that the Comcast network has a problem between these hours:

 

Comcast network outage over two nights

 

Comcast should assign a Network Engineer to fix this problem - it has been three weeks of this already. 

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

ArberA  - your traceroutes show packets being dropped by three Comcast routers.  Anytime you see an asterisk (a "*") in the traceroute, it indicates a bad or missing response from that unit (or sometimes it is due to one of the previous routers).  In your case, you have three routers in the Comcast chain showing asterisks, so I think it's pretty clear that your first three levels of Comcast routers are malfunctioning.

 

Your ping results show high ping sometimes - I see you are using Windows CMD to do the pings - try using "ping -t" which will ping forever until you CTRL-C, that will give you a longer run of ping test for reporting.

 

You also have a Comcast problem that is very similar to mine.

 

I suspect that Comcast has been playing with new QoS technology that is malfunctioning.  Because only very few of their staff understand how their networks actually work, we their customers have to put up with layer on layer of poorly trained support people for weeks on end until we blunder into someone who can actually do something about this.  Keep up the work and pressure - I believe there is someone inside of Comcast who actually can fix this.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Comcast finally put the Network team to work on this and here is what I've got so far:

 

Good – are these statistics monitored somewhere?

I'd like to think that when this happens, a customer shouldn't have to find it for you.  It's going to be rare that you will find a customer like me who will spend 100+ hours on this over three weeks, mostly communicating through the support center in Cebu, Philippines…

- L

From: "X@cable.comcast.com>
Date: Monday, July 22, 2013 8:38 AM
Subject: RE: Escalation needed - third attempt - 15 hours on phone so far

Yes it does currently at this time we do see the HUMP on the return path, so it sounds like it builds up at night time and self clears sometime during the day.
 
Sent: Monday, July 22, 2013 8:29 AM
To: X
Subject: Re: Escalation needed - third attempt - 15 hours on phone so far
 
OK – sounds good.  Does it correlate with the time of day?  These data are conclusive: right at 8:40PM it starts and right at 5AM it ends…
 
- L
 
From: X@cable.comcast.com>
Date: Monday, July 22, 2013 8:27 AM
Subject: Re: Escalation needed - third attempt - 15 hours on phone so far
 
Good morning L, 
We currently have our Network team on site and we do have an issue in the return path with elevated noise as soon as our Network team fixes the issue I'll send you a e-mail.
 
X

Sent from my iPhone

 

Contributor
kbm87
Posts: 9
Registered: ‎07-22-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I am experiencing the same issues and they started for me on Friday (7/19). I am seeing huge lag spikes to the point that online games are unplayable. I ran a trace route and several path pings to my game server and they showed high latency (200-1400ms+) at several Comcast hops in addition to packet loss.

 

Phone support has been useless and all they want to do is send out a tech. I do not have time to take off work for this, especially since it's clear that the issue is not with my equipment.

 

I would really, really appreciate a response from an admin or Comcast rep on this. It should be escalated to the internal network ops team.

New Visitor
lordobsidian
Posts: 3
Registered: ‎07-22-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

[ Edited ]

Same exact problem for me I am in Fremont, CA its been ruining my weekdays starting at 9:00 pm and lasting to about 5am in the morning, then sometimes it will happen intermittently all day. How is it that comcast cannot monitor wether their equipment is dropping scavenger or best effort packets? I would think there would be alarms hitting consoles, tickets being generated, something fellas!

 

So freaking tired of talking to useless techs doing line tests when clearly the problem is the internal network, i have given out core router names, IP addresses tied specifically to their network equipment and it takes forever for someone to look at things and only because i went balistic last time and threatened to cut off service.

 

Its a useless exercise in futility, i ended up getting a back up internet connection so i could work from home in peace in case comcast decides to belly up on me.

 

As you can see the issue is occuring right now at 11:14am PST.

 

 

Reply from 74.125.239.104: bytes=32 time=28ms TTL=53

Reply from 74.125.239.104: bytes=32 time=15ms TTL=53

Reply from 74.125.239.104: bytes=32 time=15ms TTL=53

Reply from 74.125.239.104: bytes=32 time=17ms TTL=53

Reply from 74.125.239.104: bytes=32 time=16ms TTL=53

Reply from 74.125.239.104: bytes=32 time=45ms TTL=53

Reply from 74.125.239.104: bytes=32 time=3780ms TTL=53

Reply from 74.125.239.104: bytes=32 time=17ms TTL=53

Reply from 74.125.239.104: bytes=32 time=2208ms TTL=53

Reply from 74.125.239.104: bytes=32 time=21ms TTL=53

Reply from 74.125.239.104: bytes=32 time=26ms TTL=53

Reply from 74.125.239.104: bytes=32 time=20ms TTL=53

Reply from 74.125.239.104: bytes=32 time=3217ms TTL=53

Reply from 74.125.239.104: bytes=32 time=147ms TTL=53

Reply from 74.125.239.104: bytes=32 time=16ms TTL=53

Reply from 74.125.239.104: bytes=32 time=42ms TTL=53

Reply from 74.125.239.104: bytes=32 time=51ms TTL=53

Reply from 74.125.239.104: bytes=32 time=37ms TTL=53

Reply from 74.125.239.104: bytes=32 time=24ms TTL=53

Request timed out.

Reply from 74.125.239.104: bytes=32 time=1591ms TTL=53

Reply from 74.125.239.104: bytes=32 time=18ms TTL=53

Reply from 74.125.239.104: bytes=32 time=15ms TTL=53

Reply from 74.125.239.104: bytes=32 time=17ms TTL=53

Ping statistics for 74.125.239.104:     Packets: Sent = 87, Received = 85, Lost = 2 (2% loss), Approximate round trip times in milli-seconds:     Minimum = 15ms, Maximum = 3780ms, Average = 146ms

New Visitor
mbrandenberger
Posts: 1
Registered: ‎07-22-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I have been following topics like these for about 2 weeks now and am pretty dispointed there has not been a fix yet. It makes playing games online almost impossible. If I play any Fps's it really makes it hard. constant rubberbanding and blinking around the map.

Contributor
Posts: 6
Registered: ‎09-29-2008

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I finally reported the problem, so now I have to go through the useless exercise of a tech coming out here.

 

There is no pattern to the slow times -- happens randomly all day and night and changes by the minute, but it's mostly slow.

 

What's a normal ping time? I haven't seen any of the high numbers others here are showing, but the problem comes and goes and I haven't tried pinging yet at a particularly slow time. Here are some sample pings:

 

Ping has started…

 

PING www.google.com (74.125.225.178): 56 data bytes

64 bytes from 74.125.225.178: icmp_seq=0 ttl=51 time=40.350 ms

64 bytes from 74.125.225.178: icmp_seq=1 ttl=51 time=42.857 ms

64 bytes from 74.125.225.178: icmp_seq=2 ttl=51 time=39.849 ms

64 bytes from 74.125.225.178: icmp_seq=3 ttl=51 time=43.407 ms

64 bytes from 74.125.225.178: icmp_seq=4 ttl=51 time=43.094 ms

64 bytes from 74.125.225.178: icmp_seq=5 ttl=51 time=43.163 ms

64 bytes from 74.125.225.178: icmp_seq=6 ttl=51 time=45.219 ms

64 bytes from 74.125.225.178: icmp_seq=7 ttl=51 time=40.057 ms

64 bytes from 74.125.225.178: icmp_seq=8 ttl=51 time=42.515 ms

64 bytes from 74.125.225.178: icmp_seq=9 ttl=51 time=39.352 ms

64 bytes from 74.125.225.178: icmp_seq=10 ttl=51 time=39.620 ms

64 bytes from 74.125.225.178: icmp_seq=11 ttl=51 time=37.403 ms

64 bytes from 74.125.225.178: icmp_seq=12 ttl=51 time=38.667 ms

64 bytes from 74.125.225.178: icmp_seq=13 ttl=51 time=40.950 ms

64 bytes from 74.125.225.178: icmp_seq=14 ttl=51 time=38.441 ms

64 bytes from 74.125.225.178: icmp_seq=15 ttl=51 time=40.274 ms

64 bytes from 74.125.225.178: icmp_seq=16 ttl=51 time=38.694 ms

64 bytes from 74.125.225.178: icmp_seq=17 ttl=51 time=41.148 ms

64 bytes from 74.125.225.178: icmp_seq=18 ttl=51 time=41.174 ms

64 bytes from 74.125.225.178: icmp_seq=19 ttl=51 time=42.863 ms

64 bytes from 74.125.225.178: icmp_seq=20 ttl=51 time=40.835 ms

64 bytes from 74.125.225.178: icmp_seq=21 ttl=51 time=40.712 ms

64 bytes from 74.125.225.178: icmp_seq=22 ttl=51 time=43.122 ms

64 bytes from 74.125.225.178: icmp_seq=23 ttl=51 time=40.914 ms

64 bytes from 74.125.225.178: icmp_seq=24 ttl=51 time=43.321 ms

64 bytes from 74.125.225.178: icmp_seq=25 ttl=51 time=40.740 ms

64 bytes from 74.125.225.178: icmp_seq=26 ttl=51 time=44.621 ms

64 bytes from 74.125.225.178: icmp_seq=27 ttl=51 time=39.948 ms

64 bytes from 74.125.225.178: icmp_seq=28 ttl=51 time=39.431 ms

64 bytes from 74.125.225.178: icmp_seq=29 ttl=51 time=41.905 ms

64 bytes from 74.125.225.178: icmp_seq=30 ttl=51 time=39.287 ms

64 bytes from 74.125.225.178: icmp_seq=31 ttl=51 time=56.939 ms

Request timeout for icmp_seq 32

64 bytes from 74.125.225.178: icmp_seq=33 ttl=51 time=41.757 ms

64 bytes from 74.125.225.178: icmp_seq=34 ttl=51 time=39.569 ms

64 bytes from 74.125.225.178: icmp_seq=35 ttl=51 time=40.573 ms

64 bytes from 74.125.225.178: icmp_seq=36 ttl=51 time=42.994 ms

64 bytes from 74.125.225.178: icmp_seq=37 ttl=51 time=40.414 ms

64 bytes from 74.125.225.178: icmp_seq=38 ttl=51 time=42.948 ms

64 bytes from 74.125.225.178: icmp_seq=39 ttl=51 time=39.622 ms

64 bytes from 74.125.225.178: icmp_seq=40 ttl=51 time=41.594 ms

64 bytes from 74.125.225.178: icmp_seq=41 ttl=51 time=38.977 ms

64 bytes from 74.125.225.178: icmp_seq=42 ttl=51 time=41.444 ms

64 bytes from 74.125.225.178: icmp_seq=43 ttl=51 time=40.889 ms

64 bytes from 74.125.225.178: icmp_seq=44 ttl=51 time=40.221 ms

64 bytes from 74.125.225.178: icmp_seq=45 ttl=51 time=43.179 ms

64 bytes from 74.125.225.178: icmp_seq=46 ttl=51 time=40.597 ms

64 bytes from 74.125.225.178: icmp_seq=47 ttl=51 time=40.587 ms

64 bytes from 74.125.225.178: icmp_seq=48 ttl=51 time=46.112 ms

64 bytes from 74.125.225.178: icmp_seq=49 ttl=51 time=39.236 ms

 

--- www.google.com ping statistics ---

50 packets transmitted, 49 packets received, 2.0% packet loss

round-trip min/avg/max/stddev = 37.403/41.461/56.939/2.880 ms

 

 

New Visitor
Deamian
Posts: 2
Registered: ‎07-22-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Very frustrating trying to explain that our Router/Modem (new docsis 3.0) are working fine. The lag and discos all seem to be on their end.. But everytime something happens I want to fix it on my end.. I need to stop doing that and they need to update their infrastructure.. Right at this moment im speedtesting at 6mbps  down 8mbps up, At the ultimate i've tested at 50, yeah sure. My wife is downloading something on Steam and I can't even open a web page?

 

75.99 about to go elsewhere.

New Visitor
Posts: 4
Registered: ‎07-01-2003

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I'm also in Northern Illinois. We have had sporadic outtages for the past several days. Finally on Sunday afternoon an outtage went on for hours; Philippines suggested we update to a new modem (we needed to update to docsis 3.0 anyway, right?) and by the time we got finished commissioning it, service was back. (With download times swinging wildly from 5 to 50 mbps).

 

Today the service is out again--midday, hours on end--and I dare someone in the Philippines to tell me it's my brand new modem. 

Bronze Problem Solver
Posts: 3,241
Registered: ‎05-12-2006

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping


spammy2013-1 wrote:

The outage continues – here's a plot on a logarithmic scale so you can see all of the response times.

 

To summarize: starting at 8:40PM tonight, some network event happened in the Comcast network that caused my house to lose reliable internet connectivity.  This is the same behavior we have been experiencing for several weeks now.  At night, we lose reliable internet connectivity.  In the mornings, we return to normal internet connectivity.

 

The data presented below, combined with a thorough validation of my cable modem, line and home equipment by a field technician, proves that this problem is due to Comcast's network malfunctioning. 



Did the tech check things out while there was a problem? I'm thinking this might be about your signal levels, although I don't really know enough about it to know whether or not your symptoms are consistent with a signal level problem. But if your modem and its Comcast counterpart (the CMTS) "keep trying 'till they get it right", that could explain the high response times. And the timing suggests something "close to home" rather than a problem with Comcast's Internet infrastructure.

 

The "*" in a traceroute don't really mean much; responding the way traceroute requires is a low priority for routers, and some routers are configured to never respond that way at all. But the high response times seen in the first two Comcast hops of the third traceroute at http://s23.postimg.org/ah79n32aj/tracertwhen_BAD1.jpg indicate a problem between you and the first hop. Which is why I'm thinking signal levels. So I'd check the signal levels when things are going bad. Check out the Connection Troubleshooting Tips post near the top of the list of posts.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Hi Steve - thanks for your comments but you're off base.  The timings are consistent with there being packet loss far from my modem.  14 second delays in ICMP response could be as far away as low earth orbit from my modem.

 

And WRT traceroute's accuracy - it's a tool I've used since 1989 and I understand what it means fairly well.

 

This has been confirmed as a Comcast problem, after three weeks of fighting to get noticed.

 

And now they are working to resolve the problem, but have not been keeping me updated, apart from telling me that they've located a problem in their network and are working on it.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

The problem is still occuring as shown in the plot of tonight's ping times.  It began again at almost exactly 8:40PM.

 

Comcast has not updated me on the status of the maintenance call.

 

Comcast Outage Plot 7/22

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

It looks like starting at 9:50PM the Comcast network team made some changes that caused the problem to dissappear - see the new plot below.

 

If things go like the last 5 times I've had problems like this, Comcast will simply say: "problem is fixed" and they'll never discuss what they did to cause it, or what they did to fix it.

 

Comcast outage - something changed

New Visitor
Posts: 2
Registered: ‎09-20-2009

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I have been experiencing this problem with my service as well, since 7/18.  While most noticable when watching netflixs or playing games, it does not confine itself to night occurances (though they do occur more frequently at night).

 

Just wanted to say i was still experiencing the problem as of 12noon today (7/23).  I remote in to my home pc and can checked periodically, but whatever action they took yesterday has not fulled resolved the situation.

 

Got to say, dealing with comcast support as a non novice user is nothing but frustrating.  I commend spammy2013-1 for his tenanciousness in trying to get to the right people who can actually take action.

Contributor
Posts: 6
Registered: ‎09-29-2008

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

This problem also started for me on 7/18 and currently continues as of today (7/23) here in Illinois.

New Visitor
TheSlamma
Posts: 2
Registered: ‎07-23-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Add me to the list of problems in the denver.co.denver.comcast.net area.

 

My SNR is 37 on all 8 channels, 0dBmV on all channels and 37 on the upstream PL. zero splitters, no router, DOCSIS 3.0 modem. (I do not need a tech out at my house)

 

Flawless before ~5pm, but after that when everyone gets home after work, packetloss climbs making gaming and streaming 100% unusable.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Hi all - I will be checking on my ping times tonight through the witching hour of 8:40PM before concluding that Comcast has fixed their problem.  I have not heard anything from the support team - it always seems to go this way - like they're sheepish and don't want to admit they had a problem, or don't want the real nature of the issue come to light.  I'm concerned that I need to point out where they should look next time this happens, that's why I want the RCA (root cause analysis).  At this time they've said this:

Today speaking with my Network team they where working on Bit and error rates with the Fiber NODE that serves your area and making adjustments at our San Mateo HUB. I just forward the latest DATA you have provided to me to the Network Supervisor and I'll be following up with him tomorrow and see what our next action plan is.

I've been thinking about how to make it possible for others with this kind of problem to get the same kind of evidence needed to battle through the Comcast support zombies to get to the one person that will help them.  You need a long term ping trace to an outside destination and a time graph to uncover behavior that they can correlate to their observed system behavior (if they look).

 

Following is a python program I wrote that will convert a file generated by "ping some.destin.ation > myfile" on a linux host into a plottable sequence.  It also calculates some stats on the ping data to give you an immediate sense of the damage:

#!/usr/bin/python
import fileinput
import math

f = open('pingout.csv','w+')

badping=500.0
badcount=0
count=0
minping=1000000
maxping=0
mean=0
M2=0
for line in fileinput.input():
        if len(line) == 0:
                continue
        result=line.split()
        if len(result) != 9:
            continue
        count+=1
        result=result[7]
        result=float(result.split('=')[1])
        minping=min(result,minping)
        maxping=max(result,maxping)
        delta=result-mean
        mean=mean+delta/count
        M2 = M2 + delta*(result-mean)
        if result > badping:
                badcount+=1
                print "Bad ping: %d at line %d" % ( result, count )
        f.write("{0:.1f}".format(result)+'\n')

variance=M2/(count-1)
stddev=math.sqrt(variance)
print "Min: %4.2f Max: %4.2f Avg: %4.2f StdDev: %4.2f" %  ( minping, maxping, mean, stddev )
print "The number of bad pings is %d, the total is %d" %  ( badcount, count )

 I've also thought about creating a service that would run on Amazon's servers that would provide customers of Comcast, etc with a mechanism to setup such a trace, plot it and let them point the support zombies and network engineers at it.  Thoughts?

New Visitor
Posts: 2
Registered: ‎09-20-2009

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Spammy, that's a great tool.  Might be nice to post a similar process for capturing a long term ping trace from a windows/mac machine since i dont expect a ton of folks to be running a linux box yet.

 

Also very interested to hear your results from last night.

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Well, last night was very successful - here are the ping stats:

Min: 11.00 Max: 200.00 Avg: 15.51 StdDev: 4.40
The number of bad pings is 0, the total is 55283

 A standard dev of 4.4ms on an avg ping of 15.5ms is rock solid IMO.

 

And still, I've heard nothing from the network engineer or support team about what they changed.

 

As expected... :-)

Regular Contributor
ArberA
Posts: 30
Registered: ‎06-13-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

[ Edited ]

Spammy2013-1

 

i posted a reply and have my own thread started but since this has been the best help ive read so far and your problem seems to be fixed. I think i finally got through enough people and got someone in the local dispatch branch to look at my case and should be having a supervisor and senior techs coming out to my place very soon 1day or 2 also got a point of contact now so i dont have to deal with long hours on the phone trying to get to someone who can help. i want to compile some information like you have and be able to show them in case they are here when nothing is happening which is the most likely case since it happens at night and in the early AM. Can you help me in anyway with how to go about collecting data and storing it for the next day or two to show them when they come out??

 

like to add a EDIT to my reply:

one the time this slowdown is happening is not the normal time

it seems that my download speed is fine but my upload speed is in the garbage with 0.1 mbps

my ping tests and trace routes all seem to also look good even tho i currently have no upload speed??

screen shots for reference:

Speed tests:

http://s13.postimg.org/i352wpjo7/speedtest3.jpg

http://s22.postimg.org/i9jtp1m2p/speedtest4.jpg

 

Traceroutes to google.com and cmegroup.com because they are hosted in same building 350 e cermack as comcast last servers and routers.

http://s11.postimg.org/k1mwk76wz/tracertwhen_BAD_1.jpg

http://s10.postimg.org/6e9tamjix/tracertwhen_BAD_2.jpg

 

Modem stats are fine here is screen shot when bad just so people can stop blaming line:

http://s23.postimg.org/rgkhvlid7/modemstatsslowupload.jpg

http://s10.postimg.org/lkki2ubfd/modemstatsslowupload2.jpg

 

 

 

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

I just had another high ping spike event:

Bad ping: 4425 at line 68706
Bad ping: 3425 at line 68707
Bad ping: 1425 at line 68708
Bad ping: 2425 at line 68710
Min: 9.15 Max: 4425.00 Avg: 15.69 StdDev: 21.97
The number of bad pings is 4, the total time is 23.45 hours

 One spike event doesn't make a crisis, but it shows the need to keep on top of Comcast...

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

Comcast thinks there's someone in my neighborhood spamming the line with noise:

Today when I was talking to my Network team, we are under the impression that someone in your neighborhood is back feeding some impulse noise to the system we have since then trapped out seven customers where we were picking up leaks and set up service calls to get access to those address. I’m still working with my network team daily and sharing information that you have provided me, in my opinion this problem is in our Network and we are monitoring daily, as I get more information I will keep you in the loop Mr. XYZ.

This gives me the impression that the local support supervisor who is writing this e-mail is still fighting an internal battle over whether this is their problem or not.

 

Here are the current stats:

Bad ping: 4425 at time ( 2013-07-24 11:58:06 )
Bad ping: 3425 at time ( 2013-07-24 11:58:07 )
Bad ping: 1425 at time ( 2013-07-24 11:58:08 )
Bad ping: 2425 at time ( 2013-07-24 11:58:10 )
Bad ping: 3690 at time ( 2013-07-24 17:55:41 )
Bad ping: 2690 at time ( 2013-07-24 17:55:42 )
Bad ping: 690 at time ( 2013-07-24 17:55:43 )
Bad ping: 1690 at time ( 2013-07-24 17:55:44 )
Min: 9.15 Max: 4425.00 Avg: 15.79 StdDev: 25.83
The number of bad pings is 8, last time in records: ( 2013-07-24 19:55:00 )

 

Bronze Problem Solver
Posts: 3,241
Registered: ‎05-12-2006

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping


spammy2013-1 wrote:

Comcast thinks there's someone in my neighborhood spamming the line with noise:

Today when I was talking to my Network team, we are under the impression that someone in your neighborhood is back feeding some impulse noise to the system we have since then trapped out seven customers where we were picking up leaks and set up service calls to get access to those address. I’m still working with my network team daily and sharing information that you have provided me, in my opinion this problem is in our Network and we are monitoring daily, as I get more information I will keep you in the loop Mr. XYZ.

This gives me the impression that the local support supervisor who is writing this e-mail is still fighting an internal battle over whether this is their problem or not.

____________________

 

It looks to me like he's saying that he's quite sure that it's their problem, but since he doesn't yet know exactly what the problem is he wouldn't bet his life on it. What he's saying is consistent with the traceroutes you've posted, especially the ones that showed high response times from the first few hops. And with what I was thinking.

 

This is probably ridiculous, but I'm going to throw it out there anyway. Any correlation between your problems and streetlights going on and off in your neighborhood?

Regular Contributor
spammy2013-1
Posts: 38
Registered: ‎07-20-2013

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

No streetlights in my neighborhood, but that's interesting.

 

What's even more interesting is that right when the network engineers were attached to the problem, the problem stopped - the very night they were looking into it, at 9:50PM and I have the continuous ping trace that proved it.

 

So - at this point, what I'm most interested in is finding out what they did.  As with the last 5 times I've had experiences like this with Comcast over the last 10 years, I spend a huge amount of time getting the network people involved, they fix their problem, and I never hear about what they did to fix it...

Regular Contributor
Posts: 44
Registered: ‎09-22-2008

Re: Intermittent lag / high ping - traced to a Comcast core router, verified by ping

[ Edited ]

This thread is quite interesting.  I'm currently involved in a months long battle with Comcast over a known area issue (not in my house) that's causing the downstream power levels of the higher frequencies (300 mHz+) to drop off.  The lastest bout started on 7/22.  A tech has escaleted to a maintenance crew yet again.

 

Here's what I find interesting to this thread ... This latest power issue is coupled with periods of complete packet loss to the nearest Comcast hop every night at the same time.  Monday 7/22, right around 8:30 to 8:40 PM EST, my internet drops 75 to 100% packets to my local hop.  This continues on and off for hours.  I usually leave for work before 6AM, but I saw the issue start clearing up around 5:45 AM.  Tueday 7/23, right around 8:40 PM, same thing.  Last night (7/24), I started running a ping to the 1st hop past my moden and router ... sure enough as it got near 8:30 to 8:40, the packet drops happen again.

 

I'm just north of Philly in Bucks County, but it just seems strange that the times seem to match what's being listed in this thread.  Hopefully it's all realated to the downstream power issue and will get resolved by the maintence crew.  If not, who the heck can I contact to get this issue resloved?  There doesn't seem to be much direct contact anymore on this forum or on broadbandreports.com .  Even if we can help trouble shoot the issue, there doesn't seem to be anyone at Comcast to help fix things.