Repeated 90k error

[Raist]

Country: USA
ISP: TimeWarner
Server: Hyperion

.... and yes, using WTFast ---- no difference

Constant 90k every 10-30 minutes... and 2002 since

and its not just one weekend ... this has been going on for 6 days now for me

Depending on where you are, it could be your local nodes. TWC has been having issues with oversold markets for quite some time now. Mine (Florence) was one such market...it took a lot of complaints to make it happen, but we eventually got them to split us up to different gateways to thin out some of the congestion, but it's still there. I was going through a gateway assigned to Hilton Head for about 3 months, and am now on one assigned to Conway. They're still struggling with problems here in South Carolina, but at least they are working on it.

Similar issues have been reported in Charlotte, Raleigh-Durham, Atlanta, Austin, and a host of other areas as well. You can track some of the reports at the downdetector site(can find others on their Companies list), as well as TWC's own forums. If you are comfortable with doing some tracerts and capturing your modem logs/signal pages you can try posting in their forums or contacting them through their TWCableHelp email. You can also try their Facebook and Twitter--links are posted at that downdetector page. Ultimately, what you need to do is get through to Tier3 support, as they are the ones that can call for the escalation needed to investigate this properly and pull in the engineers and such.

Just for a quick reference, here's their most recently archived status map (updates periodically throughout the day):

https://downdetector.com/status/time-warner-cable


And here's a tracert to the IP I use for Midgard. It only took 2 traces to capture the lag spike on the Conway gateway--if I ping it directly, it happens at roughly 1 in 10 pings. It's a cause for some heavy jitter at times.

C:\Windows\System32>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1     2 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    21 ms    30 ms   153 ms  cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
  3    23 ms    17 ms    25 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    18 ms    19 ms    19 ms  24.31.196.212
  5    21 ms    23 ms    21 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    27 ms    25 ms    27 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  7    24 ms    27 ms    26 ms  107.14.19.99
  8    26 ms    26 ms    27 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  9    26 ms    26 ms    25 ms  be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
 10    33 ms    34 ms    36 ms  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
 11    39 ms    40 ms    43 ms  be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
 12    43 ms    45 ms    44 ms  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
 13    50 ms    48 ms    48 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 14    64 ms    64 ms    73 ms  38.122.42.34
 15    46 ms    90 ms    48 ms  192.34.76.10
 16    48 ms    50 ms    48 ms  199.91.189.242
 17    47 ms    46 ms    49 ms  199.91.189.30

Trace complete.

During primetime, I get spikes coming through Atlanta and Chicago as well, and when they stack I can hit 1/4 second lag once in a while. Before I got TWC working on this last year, I was getting over 2 seconds of lag at times, which could cause disconnects.

I once tracked upwards of 60ms jitter to LA, which has a response time of around 60ms--that night it was showing a consistent 100% variance in lag on average. All bacause of issues at my local segments. TWC had a bucket truck on the street the NEXT day because of that crap--problems at the pole I guess.

The point is, there are known issues with TWC's networks that may be at play... until you provide them with information, you likely won't get them addressed if they are happening in your area.