Very High Latency and Jitter

What do the Zoom modem's RF error log entries look like ? Please post all of the signal status figures as well for us to see. Take a screenshot or copy and paste the text.

EG,  my modem does not keep an RF error log, or at least it's not available through the admin screens.  Here's the connection info:

I had that modem, and it always did, unless something has changed !

---

@Elliott_James wrote: ... my modem does not keep an RF error log, or at least it's not available through the admin screens. ...

---

My 5341J has one but to reach it, I have to log in, and then click bookmarked link http://192.168.100.1/RgEventLog.asp.

BruceW: thanks for the link... there's only a handful of error reports over the last few weeks:

To show how bad my connection is, here's the pings from home to the remote work site

(I'm using a UDP VPN. The remote IP address is virtual)

VIA COMCAST

64 bytes from 10.144.251.121: icmp_seq=1 ttl=64 time=3036 ms
64 bytes from 10.144.251.121: icmp_seq=2 ttl=64 time=2075 ms
64 bytes from 10.144.251.121: icmp_seq=3 ttl=64 time=1328 ms

VIA VERIZON SMARTPHONE TETHER

64 bytes from 10.144.251.121: icmp_seq=1 ttl=64 time=88.6 ms
64 bytes from 10.144.251.121: icmp_seq=2 ttl=64 time=68.8 ms
64 bytes from 10.144.251.121: icmp_seq=3 ttl=64 time=92.8 ms

What in the Comcast chain is holding my  packets for so long?

---

@Elliott_James wrote: ... there's only a handful of error reports over the last few weeks: ...

---

Not sure what to make of the event log. Three "Unicast Maintenance Ranging - No Response" entries in 10 days doesn't seem excessive. OTOH I've never seen "ToD Request sent - No Response" messages in my 5341's log, and it's been running for 6 years. A difference in the CMTS config possibly? Perhaps @EG can offer some insight.

Ping tells us that the RTT is high, but that's all. Can you run a Tracert (Windows) or Traceroute (Mac and *nix) to the target IP and post those results? That might allow us to see where the slowdown is.

---

@BruceW wrote:

---

@Elliott_James wrote: ... there's only a handful of error reports over the last few weeks: ...

---

Not sure what to make of the event log. Three "Unicast Maintenance Ranging - No Response" entries in 10 days doesn't seem excessive. OTOH I've never seen "ToD Request sent - No Response" messages in my 5341's log, and it's been running for 6 years. A difference in the CMTS config possibly? Perhaps @EG can offer some insight.

 

Ping tells us that the RTT is high, but that's all. Can you run a Tracert (Windows) or Traceroute (Mac and *nix) to the target IP and post those results? That might allow us to see where the slowdown is.

---

Here's the WinMTR (similar to Tracert) that I ran at the remote site probing my home IP

You can see mostly all is well until I hit the last hop:

|-----------------------------------------------------------------------------------------------|
|                                           WinMTR statistics                                   |
|                            Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|-----------------------------------------------------|------|------|------|------|------|------|
| [Remote]                         192.168.1.1 -    0 |   52 |   52 |    0 |    0 |    0 |    0 |
|                                     XX.X.X.X -    0 |   52 |   52 |    0 |    0 |   24 |    0 |
|001.XXX-93-216-nokia-dsl.dynamic.surewest.net -    0 |   52 |   52 |   12 |   24 |   50 |   17 |
|        133.161-60-66-biz-static.surewest.net -    2 |   50 |   49 |   13 |   25 |   67 |   18 |
|                               204.154.217.70 -    2 |   50 |   49 |   14 |   25 |   61 |   29 |
|                              204.154.217.247 -    0 |   52 |   52 |   13 |   28 |   54 |   13 |
|                              204.154.217.168 -    2 |   50 |   49 |   12 |   30 |  159 |   20 |
|                       sjo-b21-link.telia.net -    5 |   49 |   47 |    0 |   25 |   47 |   24 |
|                      palo-b24-link.telia.net -    5 |   49 |   47 |   22 |   32 |  153 |   32 |
|   be-200-pe11.529bryant.ca.ibone.comcast.net -    2 |   50 |   49 |   20 |   33 |   60 |   26 |
|  be-3111-cr02.sunnyvale.ca.ibone.comcast.net -    0 |   52 |   52 |   24 |   37 |  168 |   25 |
|    ae-79-ar01.sacramento.ca.ccal.comcast.net -    0 |   52 |   52 |   24 |   39 |  168 |   25 |
|   ae-2-rur101.sacramento.ca.ccal.comcast.net -    0 |   52 |   52 |   22 |   47 |  569 |   24 |
|                                68.87.212.158 -    2 |   50 |   49 |   23 |   35 |   75 |   42 |
| [Home]    c-XX-XX-XX-XXX.hsd1.ca.comcast.net -    0 |   52 |   52 |  131 | 1008 | 2112 |  304 |
|_____________________________________________________|______|______|______|______|______|______|

Wow -- problem completely fixed with a modem restart.  I should have done that first before starting this thread.  Sorry to waste everyone's time.  Lesson learned: when there's a connectivity issue, step 1, restart modem, every time!