TechSpot

Massive latency spikes on Wired and Wireless Connection

By Neoteric00
Mar 13, 2016
Post New Reply
  1. Could someone take a look at these ping reports and tell me what to do next? I tested both twc and yahoo, same results. I have a Netgear N450 Modem/router combo (firmware is up to date), I have Time Warner Cable, and this has been happening consistently for over 2 months. It happens every couple minutes, consistently, always. At first I assumed it was just a hiccup with my playstation 4's connection when playing online, but then I started pc gaming and realized how bad this was.

    C:\Users\Jason>tracert twc.com

    Tracing route to twc.com [71.74.189.86]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 29 ms 30 ms 15 ms cpe-67-247-216-1.buffalo.res.rr.com [67.247.216.1]
    3 106 ms 21 ms 21 ms tge0-0-0.spvlnyxx02h.northeast.rr.com [98.0.0.89]
    4 20 ms 26 ms 31 ms 24.58.38.190
    5 12 ms 12 ms 11 ms agg34.lncsnycd02r.northeast.rr.com [24.58.38.176]
    6 12 ms 15 ms 15 ms be29.rochnyei01r.northeast.rr.com [24.58.32.62]

    7 26 ms 27 ms 32 ms bu-ether25.chcgildt87w-bcr00.tbone.rr.com [107.14.19.28]
    8 57 ms 55 ms 55 ms bu-ether11.chctilwc00w-bcr00.tbone.rr.com [66.109.6.21]
    9 50 ms 50 ms 50 ms bu-ether5.enwdcocd02w-bar01.tbone.rr.com [66.109.1.51]
    10 49 ms 53 ms 50 ms 24.161.254.58
    11 1718 ms 50 ms 56 ms 71.74.189.86
    12 52 ms 50 ms 50 ms 71.74.189.86

    Trace complete.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Jason>ping twc.com -t

    Pinging twc.com [71.74.189.86] with 32 bytes of data:
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=52ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=47ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=52ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=1200ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=52ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=57ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=2461ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=48ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=51ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=50ms TTL=52
    Reply from 71.74.189.86: bytes=32 time=49ms TTL=52

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Jason>ping yahoo.com -n 100

    Pinging yahoo.com [206.190.36.45] with 32 bytes of data:
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=124ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=2452ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=104ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=104ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=94ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=3870ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=100ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
    Reply from 206.190.36.45: bytes=32 time=92ms TTL=42

    Ping statistics for 206.190.36.45:
    Packets: Sent = 98, Received = 98, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 3870ms, Average = 154ms
     
  2. Cycloid Torus

    Cycloid Torus TS Evangelist Posts: 1,655   +308

    Based on what you have captured ping and tracert, you would think it is a TWC issue.

    However, to really prove that you need to show ping at the second hop [67.247.216.1] simultaneously with ping of a further ip (ie, proving that there is no interruption between you and the ISP while there is at the same time an interruption further out into the ISPs network).

    Good background on troubleshooting your own end. http://www.tomshardware.com/answers/id-2017030/ping-spikes-wired-wireless-connections.html
     
  3. Cycloid Torus

    Cycloid Torus TS Evangelist Posts: 1,655   +308

  4. Neoteric00

    Neoteric00 TS Rookie Topic Starter

    Ok, I simultaneously pinged my router and 4.2.2.2 at the same time. They both had the issue.

    on my router I got 2,335ms and on the second I got 2,517ms

    Edit: When I ran it on my router, 4.2.2.2, and 67.247.216.1 at the same time, the ping was highest on my router when it spiked. Not sure if that indicates anything.
     
    Last edited: Mar 14, 2016
  5. Cycloid Torus

    Cycloid Torus TS Evangelist Posts: 1,655   +308

    So that makes me think it could be your drivers, your NIC, your cabling (if wired), your signal (if wireless) or your router.
     
  6. Neoteric00

    Neoteric00 TS Rookie Topic Starter

    The router firmware is only update-able from TWC, and it is the newest version. Not sure if there is anything I can do about it. I guess I will try changing cables. It was wired btw.
     
  7. Neoteric00

    Neoteric00 TS Rookie Topic Starter

    Well, thanks to you and a bit of a lightbulb moment I figured it out. It was my PLEX media server. Apparently the DLNA settings can cause huge lag spikes. Who knew???

    Thanks! Problem solved!
     
  8. jobeard

    jobeard TS Ambassador Posts: 9,310   +617

    Great * * * HANKS for the feedback as that will help others :) (y)
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...