HUGE CONNECTION PROBLEM

[Raist]

yup that would probably be it near stl charter hub and charter is only cable provider here,
tracerouting the ip my client uses only 5 ms difference in response times, no * events

Might want to submit a formal ticket to SE then...and give them that tracert data. Last fall Time Warner caught what they thought was potentially a VLAN issue on the other side of Ormuco that was a potential problem (inside the SE/Ormuco "sphere of influence" it was pegging over 200ms periodically when the rest of the route was always under 100 during their testing). They forwarded their findings to Ormuco's admin email and I submitted the data to SE through the support portal--and it cleared up like 3 days later (and we haven't seen the issue since either).

It's worth a shot since you have the actual road map (tracert) for them to look at. Probably one of the biggest problems we've run up against with these issues...lots of people complaining but not enough people submitting useful data to the people that may be able to actually do something about it.

Edit:
grrr....popped in during my lunch break to reload the market and send retainers back out and was getting a bit of stutter not usually there. Took two runs to catch it, but looks like something may be up with TATA right now.

Mom was streaming to the Roku downstairs (she finally learned how to look things up on 1CH and can't get her off the d@mn thing now) which can cause some wonkiness, but it's never been too impactful. Still dealing with a bit of weirdness getting around to Columbia---they've been wrangling with gateway problems in SC for a while now, so it's kind of normal these days. So long as I stay in a decent range things are OK. What first caught my eye was the stray * spike coming out of Ashburn towards Montreal (think that was Albany last time I checked) and then a 107 spike from 54 right after the hand-off into Ormuco-Montreal that concerns me. Not game-breaking for me yet since I'm so close... but it may be something for people further out to keep an eye on if it continues acting up. If it gets much worse TWC often cuts me over to Cogent or Level3 for a bit---usually have to hit up near 200ms for them to cut me over though. Will have to see what happens by the time I get home tonight.

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    41 ms    43 ms    49 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    35 ms    31 ms    36 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    15 ms    12 ms    13 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    27 ms    26 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    34 ms    31 ms    33 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    30 ms    29 ms    29 ms  0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
  8    30 ms    29 ms    32 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    52 ms    54 ms    53 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    52 ms    52 ms    54 ms  64.86.85.1
 11    50 ms    54 ms    53 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    51 ms    53 ms    53 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    51 ms    53 ms    53 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    51 ms    53 ms    54 ms  66.198.96.50
 15    53 ms    53 ms    53 ms  192.34.76.2
 16    52 ms    52 ms    54 ms  199.91.189.234
 17    51 ms    55 ms    51 ms  199.91.189.30

Trace complete.

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    34 ms    27 ms    26 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    28 ms    64 ms    38 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    29 ms    14 ms    15 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    28 ms    25 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    31 ms    33 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    28 ms    30 ms    29 ms  0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
  8    53 ms    56 ms    46 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    52 ms    54 ms    53 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10     *       54 ms    55 ms  64.86.85.1
 11    53 ms    55 ms    52 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    51 ms    52 ms    54 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    51 ms    52 ms    53 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    53 ms    53 ms    54 ms  66.198.96.50
 15    54 ms   107 ms    55 ms  192.34.76.2
 16    55 ms    54 ms    55 ms  199.91.189.234
 17    54 ms    53 ms    52 ms  199.91.189.30

Trace complete.