Error 90000 (90k) and others relating to it

[Xruptor]

So, coming back to this after a couple more days of unstable connections, and finally figured out how to get the exact IP address (thanks X! Though on my machine, it's Resource Monitor, not Manager) which for Ragnarok is 199.91.189.51. My problem now is that the pathping doesn't even appear to be going through to Ragnarok at all...it seems to be going through Level3 and stopping on one of their Montreal servers. There's minimal loss on the way, 1-3 % if any. My question now is....what the heck does this mean? o.O

See and that's the difference, I tried your IP address for your server Ragnarok. It turns out my connection doesn't go through Level 3 at all and only goes through one Montreal server. I get zero packet loss and don't have any disconnection issues. Which is the same thing I get for the Adamantoise server. I'm really starting to think it's Level 3.

[Unseen_Depths]

Alright I don't know much about this but the game is unplayable on my end and this just started after being fine for months. I'm on diablos and here is the information I was able to obtain. I know very little about this but I seem to be seeing quite a bit of lost on here. What can I do to fix it or who do I need to call?

Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Chase-PC.carolina.rr.com [192.168.
0.2]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
5/ 100 = 5% |
2 23ms 5/ 100 = 5% 0/ 100 = 0% cpe-024-074-176-001.carolina.res.r
r.com [24.74.176.1]
0/ 100 = 0% |
3 13ms 5/ 100 = 5% 0/ 100 = 0% cpe-024-074-253-209.carolina.res.r
r.com [24.74.253.209]
0/ 100 = 0% |
4 19ms 5/ 100 = 5% 0/ 100 = 0% ae18.rlghncpop-rtr1.southeast.rr.c
om [24.93.64.4]
0/ 100 = 0% |
5 25ms 5/ 100 = 5% 0/ 100 = 0% 107.14.19.44
0/ 100 = 0% |
6 25ms 5/ 100 = 5% 0/ 100 = 0% ae-4-0.a0.lax91.tbone.rr.com [66.1
09.1.113]
1/ 100 = 1% |
7 23ms 51/ 100 = 51% 45/ 100 = 45% ix-17-0.tcore2.AEQ-Ashburn.as6453.
net [216.6.87.149]
0/ 100 = 0% |
8 23ms 6/ 100 = 6% 0/ 100 = 0% if-2-2.tcore1.AEQ-Ashburn.as6453.n
et [216.6.87.2]
0/ 100 = 0% |
9 42ms 7/ 100 = 7% 1/ 100 = 1% 64.86.85.1
0/ 100 = 0% |
10 42ms 6/ 100 = 6% 0/ 100 = 0% if-10-2.tcore1.TTT-Toronto.as6453.
net [64.86.32.33]
0/ 100 = 0% |
11 43ms 6/ 100 = 6% 0/ 100 = 0% if-9-9.tcore1.TNK-Toronto.as6453.n
et [64.86.33.25]
0/ 100 = 0% |
12 46ms 6/ 100 = 6% 0/ 100 = 0% if-7-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.61]
0/ 100 = 0% |
13 45ms 6/ 100 = 6% 0/ 100 = 0% 66.198.96.50
0/ 100 = 0% |
14 48ms 6/ 100 = 6% 0/ 100 = 0% 192.34.76.2
1/ 100 = 1% |
15 46ms 7/ 100 = 7% 0/ 100 = 0% 199.91.189.234
0/ 100 = 0% |
16 45ms 7/ 100 = 7% 0/ 100 = 0% 199.91.189.38

Trace complete.

[Raist]

Alright I don't know much about this but the game is unplayable on my end and this just started after being fine for months. I'm on diablos and here is the information I was able to obtain. I know very little about this but I seem to be seeing quite a bit of lost on here. What can I do to fix it or who do I need to call?

            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Chase-PC.carolina.rr.com [192.168.
0.2]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                5/ 100 =  5%   |
  2   23ms     5/ 100 =  5%     0/ 100 =  0%  cpe-024-074-176-001.carolina.res.r
r.com [24.74.176.1]
                                0/ 100 =  0%   |
  3   13ms     5/ 100 =  5%     0/ 100 =  0%  cpe-024-074-253-209.carolina.res.r
r.com [24.74.253.209]
                                0/ 100 =  0%   |
  4   19ms     5/ 100 =  5%     0/ 100 =  0%  ae18.rlghncpop-rtr1.southeast.rr.c
om [24.93.64.4]
                                0/ 100 =  0%   |
  5   25ms     5/ 100 =  5%     0/ 100 =  0%  107.14.19.44
                                0/ 100 =  0%   |
  6   25ms     5/ 100 =  5%     0/ 100 =  0%  ae-4-0.a0.lax91.tbone.rr.com [66.1
09.1.113]
                                1/ 100 =  1%   |
  7   23ms    51/ 100 = 51%    45/ 100 = 45%  ix-17-0.tcore2.AEQ-Ashburn.as6453.
net [216.6.87.149]
                                0/ 100 =  0%   |
  8   23ms     6/ 100 =  6%     0/ 100 =  0%  if-2-2.tcore1.AEQ-Ashburn.as6453.n
et [216.6.87.2]
                                0/ 100 =  0%   |
  9   42ms     7/ 100 =  7%     1/ 100 =  1%  64.86.85.1
                                0/ 100 =  0%   |
 10   42ms     6/ 100 =  6%     0/ 100 =  0%  if-10-2.tcore1.TTT-Toronto.as6453.
net [64.86.32.33]
                                0/ 100 =  0%   |
 11   43ms     6/ 100 =  6%     0/ 100 =  0%  if-9-9.tcore1.TNK-Toronto.as6453.n
et [64.86.33.25]
                                0/ 100 =  0%   |
 12   46ms     6/ 100 =  6%     0/ 100 =  0%  if-7-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.61]
                                0/ 100 =  0%   |
 13   45ms     6/ 100 =  6%     0/ 100 =  0%  66.198.96.50
                                0/ 100 =  0%   |
 14   48ms     6/ 100 =  6%     0/ 100 =  0%  192.34.76.2
                                1/ 100 =  1%   |
 15   46ms     7/ 100 =  7%     0/ 100 =  0%  199.91.189.234
                                0/ 100 =  0%   |
 16   45ms     7/ 100 =  7%     0/ 100 =  0%  199.91.189.38

Trace complete.

Format got a little out of whack with the quote flags, so I inserted the code flags around it to line it up better (put brackets [ ] around the word code at the start, and then /code at the end and it keeps more of the original format--HTML strips some spaces and tabs).

It looks like you are having trouble either getting to your area's gateway, or through it to the next hop (5% loss at hop 2). That 5% at the start compounds things all the way down the route, why you consistently see losses on down the line. While that 7th hop in the Virginia area may not have pegged 51% without this weirdness at the start, it would have still been high enough to send up a flag for investigation. You also picked up a little hiccup here and there with forwarding out in TATA that may develop into something troublesome under heavy loads.

So it looks like you have an issue close to home that needs to be addressed, as well as issues around the hand off to and through your routing partner (TATA, ones with the as6453 ID's). That is who your ISP is using to get you into and across Canada. They have the means to either address that peering issues directly, or switch you to another partner... but you need to contact people higher up the chain.

Need to contact TWC/RR (or whatever brand you ISP is using) and push to get through to their Tier3 techs. Tell them you have trace data demonstrating packet loss that you need to forward to Tier3 for analysis. They will want to send a tech on site to investigate your lines--that will be Tier1 or Tier2 support, but let them come. Your 5% could be a localized signalling issue that needs to be addressed, and they may be able to take care of that quickly. The other issue though with the peering MUST be looked at by Tier3. It may even require escalation above Tier3--but ONLY tier3 can make that determination, not the guys that answer the phone, nor the ones that come and replace your cables/ends/splitters/modem.

If they keep giving you the run around, go to their website and use their online contact options. The posted email contact may even be to the T3 department. If you are indeed a TWC customer, you can use their forums. They frequently post an email address there that will get you to T3... forget what it is, and don't have access to my laptop atm to pull it up.