Connectivity
Connectivity and managing Your Comcast Business network
Back to Top

Bad pings, lag. Possible suspect line/modem.

SOLVED
cdowell
Visitor

Bad pings, lag. Possible suspect line/modem.

This is not just limited to just today.  This happens frequently.  My Cisco phone constantly has to reconnect.

Try talking over a VPN phone while you have a >9000 ping.

 

64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=8 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=9 ttl=241 time=78.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=11 ttl=241 time=59.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=12 ttl=241 time=60.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=13 ttl=241 time=59.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=14 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=15 ttl=241 time=77.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=16 ttl=241 time=59.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=17 ttl=241 time=58.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=18 ttl=241 time=60.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=19 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=20 ttl=241 time=60.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=21 ttl=241 time=60.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=22 ttl=241 time=59.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=23 ttl=241 time=61.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=24 ttl=241 time=59.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=25 ttl=241 time=59.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=26 ttl=241 time=59.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=27 ttl=241 time=59.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=28 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=29 ttl=241 time=58.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=30 ttl=241 time=60.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=39 ttl=241 time=9532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=41 ttl=241 time=7532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=42 ttl=241 time=6532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=43 ttl=241 time=5532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=44 ttl=241 time=4532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=45 ttl=241 time=3532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=46 ttl=241 time=2532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=47 ttl=241 time=1532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=48 ttl=241 time=532 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=49 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=50 ttl=241 time=60.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=51 ttl=241 time=61.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=52 ttl=241 time=59.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=53 ttl=241 time=60.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=54 ttl=241 time=60.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=55 ttl=241 time=60.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=56 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=57 ttl=241 time=78.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=58 ttl=241 time=60.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=59 ttl=241 time=59.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=60 ttl=241 time=59.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=61 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=62 ttl=241 time=59.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=63 ttl=241 time=58.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=64 ttl=241 time=62.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=65 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=66 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=67 ttl=241 time=58.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=68 ttl=241 time=58.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=69 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=70 ttl=241 time=59.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=71 ttl=241 time=58.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=72 ttl=241 time=59.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=73 ttl=241 time=60.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=74 ttl=241 time=58.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=73 ttl=241 time=1368 ms (DUP!)
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=75 ttl=241 time=59.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=76 ttl=241 time=80.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=77 ttl=241 time=60.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=78 ttl=241 time=59.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=79 ttl=241 time=60.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=80 ttl=241 time=59.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=81 ttl=241 time=58.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=82 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=83 ttl=241 time=60.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=84 ttl=241 time=58.7 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=85 ttl=241 time=59.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=86 ttl=241 time=58.7 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=87 ttl=241 time=60.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=88 ttl=241 time=60.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=89 ttl=241 time=81.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=90 ttl=241 time=94.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=91 ttl=241 time=60.5 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=92 ttl=241 time=59.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=93 ttl=241 time=61.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=94 ttl=241 time=60.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=95 ttl=241 time=59.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=96 ttl=241 time=59.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=97 ttl=241 time=60.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=98 ttl=241 time=59.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=99 ttl=241 time=59.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=100 ttl=241 time=60.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=101 ttl=241 time=60.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=102 ttl=241 time=59.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=103 ttl=241 time=60.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=104 ttl=241 time=58.8 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=105 ttl=241 time=60.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=106 ttl=241 time=60.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=107 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=108 ttl=241 time=60.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=109 ttl=241 time=59.0 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=110 ttl=241 time=85.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=111 ttl=241 time=58.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=112 ttl=241 time=60.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=118 ttl=241 time=9132 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=120 ttl=241 time=7116 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=121 ttl=241 time=6108 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=122 ttl=241 time=5100 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=123 ttl=241 time=4092 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=124 ttl=241 time=3084 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=125 ttl=241 time=2076 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=126 ttl=241 time=1068 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=127 ttl=241 time=60.7 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=128 ttl=241 time=60.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=130 ttl=241 time=7059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=131 ttl=241 time=6059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=132 ttl=241 time=5059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=133 ttl=241 time=4059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=134 ttl=241 time=3059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=135 ttl=241 time=2059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=136 ttl=241 time=1059 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=137 ttl=241 time=59.7 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=143 ttl=241 time=6205 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=144 ttl=241 time=5197 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=145 ttl=241 time=4189 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=146 ttl=241 time=3181 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=147 ttl=241 time=2173 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=148 ttl=241 time=1166 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=149 ttl=241 time=158 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=150 ttl=241 time=69.7 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=151 ttl=241 time=59.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=152 ttl=241 time=59.4 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=153 ttl=241 time=58.9 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=154 ttl=241 time=60.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=155 ttl=241 time=59.3 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=156 ttl=241 time=59.1 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=157 ttl=241 time=60.6 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=158 ttl=241 time=60.2 ms
64 bytes from us2-sec-vpn-01.oracle-ocna.com (160.34.104.1): icmp_seq=159 ttl=241 time=59.1 ms

Accepted Solution

Re: You guys really, really, really, really? need to step it up a notch - sample ping

Dear p o,

 

You should understand that the ping command uses ICMP messages which must be processed in device CPU as opposed to the switching fabric.  In addition, ICMP messages often receive lower priority that other traffic.  All this makes ping measurements of round trip delay (RTT) problematic at best. 

 

For any given application, the most realistic RTT measurements must be made with application protocol packets.

 

The best one can conclude from your data is that there is occasional network congestion affecting ICMP ping measurements. This may or may not be correlated to application protocol problems.  More data is needed.  In fact, even the oracle address you are pinging may actually be different boxes at different times since there is no established connection.  One cannot determine this without more data. There is no indication of where the delay is actually introduced into the ping path. It is also not clear if this is a 24/day problem or limited to certain hours.

 

Having said all that, are you certain that it is Comcast causing the problem?  Have you done a traceroute to determine how many hops and what network providers are involved?  Define frequently both in duration and time of day. Let us know what you determine and we might actually be able to provide cogent advice. 

View solution in context
Trusted Forum Contributor

Re: You guys really, really, really, really? need to step it up a notch - sample ping

Dear p o,

 

You should understand that the ping command uses ICMP messages which must be processed in device CPU as opposed to the switching fabric.  In addition, ICMP messages often receive lower priority that other traffic.  All this makes ping measurements of round trip delay (RTT) problematic at best. 

 

For any given application, the most realistic RTT measurements must be made with application protocol packets.

 

The best one can conclude from your data is that there is occasional network congestion affecting ICMP ping measurements. This may or may not be correlated to application protocol problems.  More data is needed.  In fact, even the oracle address you are pinging may actually be different boxes at different times since there is no established connection.  One cannot determine this without more data. There is no indication of where the delay is actually introduced into the ping path. It is also not clear if this is a 24/day problem or limited to certain hours.

 

Having said all that, are you certain that it is Comcast causing the problem?  Have you done a traceroute to determine how many hops and what network providers are involved?  Define frequently both in duration and time of day. Let us know what you determine and we might actually be able to provide cogent advice. 

cdowell
Visitor

Re: You guys really, really, really, really? need to step it up a notch - sample ping

My apologies, venting, frustration, etc in my opener.  Attached is an mtr run to google.com.  It appears my modem or line is suspect.mtr.jpg

cdowell
Visitor

Re: You guys really, really, really, really? need to step it up a notch - sample ping

Been reading other threads, this Netgear CG3000DCR is highly suspect. 

 

Can we use our own modems?  I have a D-Link that has served me well for years I would rather use.

Trusted Forum Contributor

Re: You guys really, really, really, really? need to step it up a notch - sample ping

Maybe not totally related, maybe it is but the IP 71.200.216.1 is on four different blacklists.

 

Now I'm not focusing on that the network maybe couldn't reliably serve and receive mail but it may be an indication of flooding by local devices causing an issue here...

 

edit: this is if in fact 71.200.216.1 is your IP