dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
10
share rss forum feed

BBL

join:2013-03-13
Raleigh, NC

1 edit
reply to scififan68

Re: High latency from 8-11 PM every night in Raleigh, NC

I'm not sure if I can say that your tracert looks similar, but how you described it definitely does.

I've tried a Motorola SBG6580 (purchased on my own) and an Arris DG860A (provided by TWC). I actually purchased the Motorola since it had some of the best reviews and I was hoping it might fix (or somewhat alleviate these issues), but no luck. The Arris seems slightly better even, but both have the same issue.

Here is a graph of my 2nd and 4th hops: »i.imgur.com/jibQ4Hh.png

The 2nd hop shows some crazy spikes that I don't fully understand, but they happen 24/7 and don't really correspond to any kind of performance hits that I can feel while gaming, so I haven't been too concerned with it.

The 4th hop is where the performance hits are noticeably visible and do correspond directly to gaming performance. But as I mentioned before, the different modems will report them at different hops some reason (maybe just a flaw in the PingPlotter software?). On the Motorola, the nightly spike was not visible at hop 4, but it was at hop 3. The Arris reported lag at hop 3 three nights ago, but it has reported it at hop 4 for the last two nights.


scififan68

join:2010-10-02
Fremont, NE

Of course my tracert is different(I'm in Nebraska), but you should see a large jump of ping on one of the routers. Your modems are Docsis 3, so they aren't the issue unless you see high pings at the 2nd hop.

From your picture I can see that your third hop is fine with ping but your problem is on the 4th hop, and this would be TWC's fault.

In ping plotter you should be able to see past tracroutes to google(on top), by clicking where it shows the high pings it should show exactly where the ping is going up that high, but as I'm suspecting its hop 4.

EDIT: You should post your signals, they should be located here: »192.168.100.1/