Rookie

High ping and lag in Springfield OH today

New to this forum, how do you normally report high pings and lag?  This morning getting service 3-4 times worse than yesterday...

 

Looks like ae1.spfdoh3701h.midwest.rr.com is having issues.

 

20/11/2017 14:03:16 UTC
--------------------

MTR:
Start: Mon Nov 20 14:03:16 2017
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.70.56 0.0% 10 0.2 2.3 0.2 19.5 6.0
2.|-- 37.244.22.3 0.0% 10 0.4 0.9 0.4 3.4 0.7
3.|-- 24.105.30.158 0.0% 10 1.0 1.1 0.9 1.6 0.0
4.|-- 137.221.66.4 0.0% 10 1.4 1.5 1.4 1.9 0.0
5.|-- 137.221.68.68 0.0% 10 1.4 1.8 1.2 5.0 0.9
6.|-- 137.221.68.32 0.0% 10 1.3 3.3 1.1 17.0 5.0
7.|-- ae34.pr1.lax10.tbone.rr.com 0.0% 10 1.0 1.1 0.9 1.7 0.0
8.|-- bu-ether27.tustca4200w-bcr00.tbone.rr.com 0.0% 10 54.7 54.1 50.6 56.9 2.3
9.|-- bu-ether14.lsancarc0yw-bcr00.tbone.rr.com 0.0% 10 50.0 53.8 50.0 57.2 2.3
10.|-- bu-ether16.chctilwc00w-bcr00.tbone.rr.com 0.0% 10 57.0 53.9 50.9 57.0 2.1
11.|-- be1.clmkohpe01r.midwest.rr.com 0.0% 10 62.2 64.0 61.3 67.1 2.2
12.|-- be1.blasohdp01r.midwest.rr.com 0.0% 10 77.9 75.8 72.0 79.7 2.5
13.|-- be10.65.dytnoh5501r.midwest.rr.com 0.0% 10 78.8 76.7 72.7 80.6 2.6
14.|-- ae1.spfdoh3701h.midwest.rr.com 0.0% 10 91.6 128.9 81.9 407.4 101.7
15.|-- tg6-0.spfdoh3703m.swo.rr.com 0.0% 10 72.2 72.0 71.9 72.7 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

4 REPLIES
Expert

Re: High ping and lag in Springfield OH today

copy and paste the modems signal level and error log pages as well as a tracert to google.com.

Need to see what your path to a stable site is.

 

This may be backlash from TWC/Spectrums turning off all the analog channels last week.

There's numerous strange complaints in Ohio...

 

Rookie

Re: High ping and lag in Springfield OH today

Thanks for the reply.  This afternoon it appears back to normal.  They are definitly doing work, took them a week to fix email issues last month.  Their first level tech support is worthless.

 

Anyway posting google.com results for comparison if it happens again...

 

>tracert google.com

Tracing route to google.com [172.217.4.78]
over a maximum of 30 hops:

1 2 ms 1 ms 5 ms 192.168.3.1
2 11 ms 10 ms 11 ms 142.254.145.189
3 27 ms 31 ms 31 ms 24.29.4.241
4 15 ms 14 ms 13 ms be38.dytnoh5501r.midwest.rr.com [65.29.38.100]
5 19 ms 21 ms 21 ms be28.clevohek01r.midwest.rr.com [65.29.1.46]
6 32 ms 27 ms 31 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
7 32 ms 30 ms 30 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
8 27 ms 28 ms 35 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
9 28 ms 28 ms 28 ms ix-ae-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
10 28 ms 29 ms 27 ms 72.14.198.28
11 27 ms 30 ms 28 ms 108.170.246.49
12 28 ms 28 ms 28 ms 216.239.50.97
13 35 ms 36 ms 34 ms 209.85.253.248
14 35 ms 37 ms 36 ms 216.239.57.76
15 35 ms 35 ms 34 ms 108.170.244.1
16 36 ms 36 ms 41 ms 216.239.51.145
17 34 ms 34 ms 35 ms lga15s47-in-f78.1e100.net [172.217.4.78]

Trace complete.

>ping google.com

Pinging google.com [172.217.4.78] with 32 bytes of data:
Reply from 172.217.4.78: bytes=32 time=35ms TTL=52
Reply from 172.217.4.78: bytes=32 time=38ms TTL=52
Reply from 172.217.4.78: bytes=32 time=34ms TTL=52
Reply from 172.217.4.78: bytes=32 time=36ms TTL=52

Ping statistics for 172.217.4.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 38ms, Average = 35ms

Established Sharer

Re: High ping and lag in Springfield OH today

Neither TWC of old nor Spectrum today guarantees any specific packet losses ing or 'ping' delay times.  The ONLY criteria for bad service (and issuance of a credit on your monthly bill) is data speed across their transport network as measured using the Ookla sites hosted by Spectrum and a wired connection to the router.  If you are getting at least 80% of your plan's speeds both up and down, your connection is deemed to be working adequately.

Highlighted
Expert

Re: High ping and lag in Springfield OH today

This looks like a wireless connection:

1    2 ms 1 ms 5 ms 192.168.3.1 

 Next, need to see the signal level pages...