Established Sharer

Re: High Ping/Latency after 8pm every night

The model DIR655 router first shipped from D-Link in 2007.  That's right, its design is over ten years old, pre-SmartPhones!  The DIR-655 doesn't have dual-band wireless support.  It is equipped with a Gigabit 4 port switch and 2.4 GHz SINGLE-BAND WiFiIts SharePort USB port can work with only one computer at a time. 

Since this user is located in the NYC franchise area, his service suffers from known but unrepaired ingress in the range around 330 MHz.  If he's in a high density area of housing units, the wireless may be almost unuseable at times due to frequency congestion.   SpeedTest should only be run using an ethernet cable.

The NAT addressing looks wrong, as though the router is not getting information from the network to set up its DHCP.  If that's true, it probably also is not using TWC's DNS, resulting in high 'ping' times.

Participant

Re: High Ping/Latency after 8pm every night

i'm not using wireless  for any of the pcs, all of them are on ethernet coming from the switch.

also using google's DNS 8.8.8.8 ill go back to the twc one to see what happens after 8pm today

Established Sharer

Re: High Ping/Latency after 8pm every night

Google's DNS works great for routing to sites located on the WorldWide Web, but not while your computers are inside the TWC-Spectrum network.  Reason is that your data first has to escape TWC at an internet gateway (or IXC).  TWC can only send your data packets within their private internet backbone to those IXC locations.  There are only a handful across the entire USA where TWC bumps against the 'real' internet to hand off data to the outside world.

... And one other suggestion:

If you are running any Apple networking, computing, or iPhone devices, change the router's DHCP block to start at 11 or higher, preferably at 100.  Apple hardware is known to intermittently misbehave when the last segment of the IP address is a decimal digit from 1 to 10.

Participant

Re: High Ping/Latency after 8pm every night

8:29pm this is with the twc dns not google.

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

1 15 ms 32 ms 18 ms 142.254.161.125
2 233 ms 239 ms 237 ms be62.nycmnywi02h.nyc.rr.com [68.173.200.234]
3 200 ms 211 ms 211 ms agg116.nyquny9101r.nyc.rr.com [68.173.198.50]
4 229 ms 239 ms 240 ms bu-ether15.nycmny837aw-bcr00.tbone.rr.com [66.109.6.76]
5 208 ms 215 ms 222 ms 0.ae1.pr0.nyc20.tbone.rr.com [66.109.6.163]
6 195 ms 190 ms 204 ms ix-ae-10-0.tcore1.N75-New-York.as6453.net [66.110.96.13]
7 266 ms 258 ms 238 ms 72.14.195.232
8 * * * Request timed out.
9 270 ms 275 ms 256 ms 108.170.230.1
10 284 ms 282 ms 296 ms lga25s40-in-f14.1e100.net [216.58.219.206]

Trace complete.

 

going try only with the modem now without any router

Participant

Re: High Ping/Latency after 8pm every night

this is modem to pc only 

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

1 16 ms 19 ms 17 ms 142.254.161.125
2 469 ms 447 ms 458 ms be62.nycmnywi02h.nyc.rr.com [68.173.200.234]
3 285 ms 287 ms 275 ms agg116.nyquny9101r.nyc.rr.com [68.173.198.50]
4 265 ms 263 ms 255 ms 66.109.3.218
5 277 ms 273 ms 271 ms 0.ae0.pr0.nyc20.tbone.rr.com [66.109.6.157]
6 259 ms 287 ms 265 ms ix-ae-6-0.tcore1.N75-New-York.as6453.net [66.110.96.53]
7 277 ms 279 ms 246 ms 72.14.195.232
8 * * * Request timed out.
9 256 ms 273 ms 274 ms 216.239.62.159
10 250 ms 228 ms 273 ms lga34s15-in-f14.1e100.net [172.217.10.110]

Trace complete.

 

i don't know what else to try..

Established Sharer

Re: High Ping/Latency after 8pm every night


Redx508 wrote:

this is modem to pc only 

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

1 16 ms 19 ms 17 ms 142.254.161.125
2 469 ms 447 ms 458 ms be62.nycmnywi02h.nyc.rr.com [68.173.200.234]
3 285 ms 287 ms 275 ms agg116.nyquny9101r.nyc.rr.com [68.173.198.50]
4 265 ms 263 ms 255 ms 66.109.3.218
5 277 ms 273 ms 271 ms 0.ae0.pr0.nyc20.tbone.rr.com [66.109.6.157]
6 259 ms 287 ms 265 ms ix-ae-6-0.tcore1.N75-New-York.as6453.net [66.110.96.53]
7 277 ms 279 ms 246 ms 72.14.195.232
8 * * * Request timed out.
9 256 ms 273 ms 274 ms 216.239.62.159
10 250 ms 228 ms 273 ms lga34s15-in-f14.1e100.net [172.217.10.110]

Trace complete.

 

i don't know what else to try..


First, reset the router back to factory defaults.  It's usually a little black pushbutton or hole for a paperclip marked "RESET' on the back panel.  You may have to hold it for 30 seconds or longer before it resets.  Then run the router setup using the manufacturer-supplied install CD/DVD.

Next, check that your DIR655 router is set to allow at least 15 DHCP addresses.  

Third, see if it has the most recent firmware version installed.  You can download that and the instructions from the D-Link web site. 

Participant

Re: High Ping/Latency after 8pm every night

i tested without the router still had the same thing after 8pm

 

so it has nothing to do with router

Established Sharer

Re: High Ping/Latency after 8pm every night

Did you clear the cache history on your computer before connecting directly to the modem?  You should do that every trime you change the computer connection to a different network device (router vs modem).  In newer versions of Windows ( Win7 or higher) you may also have to 'repair' the network connection to flush the old IP addresses.  As noted earlier, you also need the proper TWC-Spectrum DNS server addresses (209.18.47.61 and 62) loaded in your computer network settings, especially when you are not connecting through your router. 

Participant

Re: High Ping/Latency after 8pm every night

the internet works 100% most of the time is just after 8pm till 12am that i get the high latency.

 

i'm thinking this is a node congestion issue with spectrum.

Highlighted
Established Sharer

Re: High Ping/Latency after 8pm every night

After reviewing your latest data, I now agree with your conclusion that extreme network congestion is causing both the ping and raw speed problems.  It's much like an oversold airline flight leaving from Newark.  Unfortunately there are no more federal rules covering internet users willing to give up their spots on the network during prime time in exchange for lower rates the rest of the day.  This is doubly true now that Ajit Pai is chairman of the FCC.  Network neutrality would have helped, but that idea is being walked back by Mr Pai so that Spectrum won't be required to fix their network problems before they can make even more profits.  You know who to thank for rolling back the rules!