Repeated 90k error

**artfulscruff** · 12-06-2014 10:09 PM

Even if that is what they're going to do, I wish they'd just say so rather than keep us in the dark.

**Ghift** · 12-06-2014 10:13 PM

Information to go with my previous post

UK | Sky Broadband (not fiber optic /cry)

Tried pinging Phoenix a few times - sometimes it's flawless, sometimes the whole thing times out.

Not having any other issues or slowness, have tried resetting and cycling the router itself.

Had the problem since perhaps 2~3am last night?

**Valio** · 12-06-2014 10:41 PM

Location: Finland
ISP: Elisa
Server: Diabolos

Massive connection issues(error 90k, 2002) since roulette reset time yesterday. Game still unplayable. Did some traces and here is result while the connection seems stable.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1     3 ms     3 ms     1 ms  vanhel1.fi.elisa.net [88.114.80.1]
  2    <1 ms    <1 ms    <1 ms  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3    <1 ms    <1 ms    <1 ms  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4    <1 ms    <1 ms    <1 ms  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5    <1 ms    <1 ms    <1 ms  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19
1.153]
  6     7 ms     7 ms     7 ms  213.192.184.201
  7     7 ms     7 ms     7 ms  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8   115 ms   115 ms   116 ms  xe-9-0-0.mtl10.ip4.gtt.net [141.136.105.162]
  9   115 ms   115 ms   116 ms  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10   115 ms   115 ms   115 ms  192.34.76.2
 11   116 ms   116 ms   116 ms  199.91.189.234
 12   116 ms   116 ms   115 ms  199.91.189.38

Trace complete.

And here is some results when I notice massive lag right before 90k.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1     9 ms     2 ms     2 ms  vanhel1.fi.elisa.net [88.114.80.1]
  2     1 ms    <1 ms    <1 ms  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3     1 ms    <1 ms    <1 ms  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4     1 ms    <1 ms    <1 ms  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5    <1 ms    <1 ms    <1 ms  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19
1.153]
  6     7 ms     7 ms     7 ms  213.192.184.201
  7     7 ms     7 ms     7 ms  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8   116 ms   116 ms   115 ms  xe-1-3-0.mtl10.ip4.gtt.net [89.149.184.74]
  9     *      116 ms     *     ormuco-gw.ip4.gtt.net [216.221.156.110]
 10   116 ms   116 ms   116 ms  192.34.76.2
 11   116 ms   116 ms   116 ms  199.91.189.234
 12     *      117 ms     *     199.91.189.38
 13   116 ms     *      116 ms  199.91.189.38

Trace complete.

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1     6 ms     1 ms     1 ms  vanhel1.fi.elisa.net [88.114.80.1]
  2     1 ms    <1 ms    <1 ms  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3     1 ms    <1 ms    <1 ms  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4    <1 ms    <1 ms    <1 ms  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5    32 ms    31 ms    28 ms  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19
1.153]
  6     7 ms     8 ms     7 ms  213.192.184.201
  7     7 ms     7 ms     7 ms  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8   118 ms   169 ms     *     xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
  9   118 ms   118 ms   118 ms  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10   118 ms   118 ms   118 ms  192.34.76.2
 11   133 ms   118 ms   122 ms  199.91.189.234
 12     *      118 ms   118 ms  199.91.189.38

Trace complete.

And pathping results showing nasty packet loss.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1  vanhel1.fi.elisa.net [88.114.80.1]
  2  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153]
  6  213.192.184.201
  7  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8  xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
  9  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10  192.34.76.2
 11  199.91.189.234
 12  199.91.189.38

Computing statistics for 300 seconds...

            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  1  ---     100/ 100 =100%   100/ 100 =100%  vanhel1.fi.elisa.net [88.114.80.1]
                                0/ 100 =  0%   |
  2    3ms     0/ 100 =  0%     0/ 100 =  0%  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
                                0/ 100 =  0%   |
  3    6ms     0/ 100 =  0%     0/ 100 =  0%  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
                                0/ 100 =  0%   |
  4    3ms     0/ 100 =  0%     0/ 100 =  0%  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
                                0/ 100 =  0%   |
  5    3ms     0/ 100 =  0%     0/ 100 =  0%  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153]
                                0/ 100 =  0%   |
  6   10ms     0/ 100 =  0%     0/ 100 =  0%  213.192.184.201
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
                               27/ 100 = 27%   |
  8  ---     100/ 100 =100%    73/ 100 = 73%  xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
                                0/ 100 =  0%   |
  9  120ms    40/ 100 = 40%    13/ 100 = 13%  ormuco-gw.ip4.gtt.net [216.221.156.110]
                                0/ 100 =  0%   |
 10  120ms    37/ 100 = 37%    10/ 100 = 10%  192.34.76.2
                                0/ 100 =  0%   |
 11  120ms    27/ 100 = 27%     0/ 100 =  0%  199.91.189.234
                                7/ 100 =  7%   |
 12  119ms    34/ 100 = 34%     0/ 100 =  0%  199.91.189.38

Trace complete.

**JamesDevice** · 12-06-2014 11:36 PM

Originally Posted by Valio

Location: Finland
ISP: Elisa
Server: Diabolos

<snip>

And pathping results showing nasty packet loss.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1  vanhel1.fi.elisa.net [88.114.80.1]
  2  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153]
  6  213.192.184.201
  7  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8  xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
  9  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10  192.34.76.2
 11  199.91.189.234
 12  199.91.189.38

Computing statistics for 300 seconds...

            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  1  ---     100/ 100 =100%   100/ 100 =100%  vanhel1.fi.elisa.net [88.114.80.1]
                                0/ 100 =  0%   |
  2    3ms     0/ 100 =  0%     0/ 100 =  0%  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
                                0/ 100 =  0%   |
  3    6ms     0/ 100 =  0%     0/ 100 =  0%  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
                                0/ 100 =  0%   |
  4    3ms     0/ 100 =  0%     0/ 100 =  0%  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
                                0/ 100 =  0%   |
  5    3ms     0/ 100 =  0%     0/ 100 =  0%  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153]
                                0/ 100 =  0%   |
  6   10ms     0/ 100 =  0%     0/ 100 =  0%  213.192.184.201
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
                               27/ 100 = 27%   |
  8  ---     100/ 100 =100%    73/ 100 = 73%  xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
                                0/ 100 =  0%   |
  9  120ms    40/ 100 = 40%    13/ 100 = 13%  ormuco-gw.ip4.gtt.net [216.221.156.110]
                                0/ 100 =  0%   |
 10  120ms    37/ 100 = 37%    10/ 100 = 10%  192.34.76.2
                                0/ 100 =  0%   |
 11  120ms    27/ 100 = 27%     0/ 100 =  0%  199.91.189.234
                                7/ 100 =  7%   |
 12  119ms    34/ 100 = 34%     0/ 100 =  0%  199.91.189.38

Trace complete.

I did a check for packet loss on my route to the SE servers. And I too have packet loss rates up to 50% at a hop run by the Internet carrier gtt (http://www.gtt.net/. The hop address in my case is

141.136.101.233 (xe-11-0-1.fra29.ip4.gtt.net)

Also, the tool PingPlotter I used to track the loss has logged multiple routing changes within the gtt network which may indicate a problem within their network.

I wonder if other peoples' traffic from the EU is routed via the carrier gtt as well?

**Raist** · 12-06-2014 11:47 PM

Originally Posted by Valio

Location: Finland
ISP: Elisa
Server: Diabolos

Massive connection issues(error 90k, 2002) since roulette reset time yesterday. Game still unplayable. Did some traces and here is result while the connection seems stable.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1     3 ms     3 ms     1 ms  vanhel1.fi.elisa.net [88.114.80.1]
  2    <1 ms    <1 ms    <1 ms  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3    <1 ms    <1 ms    <1 ms  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4    <1 ms    <1 ms    <1 ms  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5    <1 ms    <1 ms    <1 ms  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19
1.153]
  6     7 ms     7 ms     7 ms  213.192.184.201
  7     7 ms     7 ms     7 ms  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8   115 ms   115 ms   116 ms  xe-9-0-0.mtl10.ip4.gtt.net [141.136.105.162]
  9   115 ms   115 ms   116 ms  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10   115 ms   115 ms   115 ms  192.34.76.2
 11   116 ms   116 ms   116 ms  199.91.189.234
 12   116 ms   116 ms   115 ms  199.91.189.38

Trace complete.

And here is some results when I notice massive lag right before 90k.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1     9 ms     2 ms     2 ms  vanhel1.fi.elisa.net [88.114.80.1]
  2     1 ms    <1 ms    <1 ms  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3     1 ms    <1 ms    <1 ms  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4     1 ms    <1 ms    <1 ms  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5    <1 ms    <1 ms    <1 ms  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19
1.153]
  6     7 ms     7 ms     7 ms  213.192.184.201
  7     7 ms     7 ms     7 ms  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8   116 ms   116 ms   115 ms  xe-1-3-0.mtl10.ip4.gtt.net [89.149.184.74]
  9     *      116 ms     *     ormuco-gw.ip4.gtt.net [216.221.156.110]
 10   116 ms   116 ms   116 ms  192.34.76.2
 11   116 ms   116 ms   116 ms  199.91.189.234
 12     *      117 ms     *     199.91.189.38
 13   116 ms     *      116 ms  199.91.189.38

Trace complete.

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1     6 ms     1 ms     1 ms  vanhel1.fi.elisa.net [88.114.80.1]
  2     1 ms    <1 ms    <1 ms  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3     1 ms    <1 ms    <1 ms  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4    <1 ms    <1 ms    <1 ms  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5    32 ms    31 ms    28 ms  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19
1.153]
  6     7 ms     8 ms     7 ms  213.192.184.201
  7     7 ms     7 ms     7 ms  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8   118 ms   169 ms     *     xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
  9   118 ms   118 ms   118 ms  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10   118 ms   118 ms   118 ms  192.34.76.2
 11   133 ms   118 ms   122 ms  199.91.189.234
 12     *      118 ms   118 ms  199.91.189.38

Trace complete.

And pathping results showing nasty packet loss.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops

  1  vanhel1.fi.elisa.net [88.114.80.1]
  2  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
  3  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
  4  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
  5  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153]
  6  213.192.184.201
  7  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
  8  xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
  9  ormuco-gw.ip4.gtt.net [216.221.156.110]
 10  192.34.76.2
 11  199.91.189.234
 12  199.91.189.38

Computing statistics for 300 seconds...

            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  1  ---     100/ 100 =100%   100/ 100 =100%  vanhel1.fi.elisa.net [88.114.80.1]
                                0/ 100 =  0%   |
  2    3ms     0/ 100 =  0%     0/ 100 =  0%  ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50]
                                0/ 100 =  0%   |
  3    6ms     0/ 100 =  0%     0/ 100 =  0%  ae10.helpa-p1.fi.elisa.net [139.97.6.205]
                                0/ 100 =  0%   |
  4    3ms     0/ 100 =  0%     0/ 100 =  0%  ae2.helpa-gw1.fi.elisa.net [139.97.6.250]
                                0/ 100 =  0%   |
  5    3ms     0/ 100 =  0%     0/ 100 =  0%  ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153]
                                0/ 100 =  0%   |
  6   10ms     0/ 100 =  0%     0/ 100 =  0%  213.192.184.201
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  ae1-103.stk10.ip4.gtt.net [141.136.97.153]
                               27/ 100 = 27%   |
  8  ---     100/ 100 =100%    73/ 100 = 73%  xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
                                0/ 100 =  0%   |
  9  120ms    40/ 100 = 40%    13/ 100 = 13%  ormuco-gw.ip4.gtt.net [216.221.156.110]
                                0/ 100 =  0%   |
 10  120ms    37/ 100 = 37%    10/ 100 = 10%  192.34.76.2
                                0/ 100 =  0%   |
 11  120ms    27/ 100 = 27%     0/ 100 =  0%  199.91.189.234
                                7/ 100 =  7%   |
 12  119ms    34/ 100 = 34%     0/ 100 =  0%  199.91.189.38

Trace complete.

Your issues appear to be with your ISP's routing partner, specifically right around where you are exiting their network at the exchange into Ormuco. Your ISP can actually resolve this for you (or at least make an honest effort). They can either notify their partner and try to get them to address the issue on their network, or they can switch you to an alternate routing partner to see if you get a more stable route.

Thread: Repeated 90k error

Thread Tools

Search Thread

Display

Hybrid View