Cogent / Telia peering is messed up (again)

Started by jezuk1, Oct 11, 2010, 20:33:58

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

jezuk1

Oct 11, 2010, 20:33:58
This was an issue about a month ago, and the problem is back again. World of Warcraft lag is huge (400ms+) and basically unplayable.

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    25 ms    25 ms    24 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    25 ms    24 ms    25 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
 4    25 ms    25 ms    25 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
 5    25 ms    25 ms    25 ms  te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
 6    25 ms    25 ms    26 ms  te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
 7    25 ms    25 ms    25 ms  te1-7.mpd01.lon01.atlas.cogentco.com [130.117.2.25]
 8   138 ms     *      137 ms  ldn-b4-link.telia.net [213.248.70.237]
 9   137 ms   137 ms     *     ldn-bb1-link.telia.net [80.91.251.18]
10   145 ms     *      145 ms  prs-bb1-link.telia.net [80.91.247.254]
11   146 ms   151 ms   146 ms  prs-b4-link.telia.net [213.248.65.226]

jezuk1

#2
Oct 11, 2010, 21:56:38 Last Edit: Oct 11, 2010, 22:13:30 by jezuk1
Why is this happening again? It's happened before, it's happened again.... What's to say it won't happen in the future. There is obvioulsly a recurring problem here. Can we please have some information about what's going on? When will it be fixed?

Steve

#3
Oct 11, 2010, 22:13:43
It not localised to Idnet though, below is tracert with similar lag from a non Idnet customer.

http://www.idnetters.co.uk/forums/index.php?topic=22471.msg540747#msg540747
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

sof2er

#4
Oct 11, 2010, 22:22:25
Quote from: Steve on Oct 11, 2010, 22:13:43
It not localised to Idnet though, below is tracert with similar lag from a non Idnet customer.

http://www.idnetters.co.uk/forums/index.php?topic=22471.msg540747#msg540747

His end destination has a 44 ms ping, he's not affected.

Steve

#5
Oct 11, 2010, 22:26:05
Sorry I should have looked more closely.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Nova

#6
Oct 11, 2010, 22:29:10
Definitely looks to be Cogent's peering that's buggered, Blizzard's support people will inform us to pester the ISP and have them pester their peer to resolve this.

esh

#7
Oct 11, 2010, 23:54:31
I can confirm this seems slightly off.

Code Select

traceroute to 213.248.65.226 (213.248.65.226), 30 hops max, 40 byte packets
1  192.168.1.3 (192.168.1.3)  0.482 ms  1.270 ms  1.477 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  12.019 ms  12.993 ms  14.481 ms
3  telehouse-gw5-e4-400.idnet.net (212.69.63.245)  15.973 ms  19.194 ms  20.672 ms
4  gi8-27.mpd01.lon02.atlas.cogentco.com (149.6.148.205)  22.418 ms  24.146 ms  25.654 ms
5  te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117)  27.130 ms  29.355 ms  30.084 ms
6  te4-2.ccr01.lon01.atlas.cogentco.com (130.117.1.201)  31.573 ms te9-2.mpd02.lon01.atlas.cogentco.com (130.117.48.153)  8.874 ms te4-2.ccr01.lon01.atlas.cogentco.com (130.117.1.201)  9.180 ms
7  te2-2.mpd01.lon01.atlas.cogentco.com (130.117.1.74)  152.528 ms te1-7.mpd01.lon01.atlas.cogentco.com (130.117.2.25)  152.927 ms te2-2.mpd01.lon01.atlas.cogentco.com (130.117.1.74)  152.846 ms
8  ldn-b4-link.telia.net (213.248.70.237)  164.501 ms  164.713 ms  164.772 ms
9  ldn-bb2-link.telia.net (80.91.249.133)  132.016 ms ldn-bb2-link.telia.net (80.91.250.238)  133.952 ms ldn-bb2-link.telia.net (80.91.251.14)  134.934 ms
10  prs-bb2-link.telia.net (80.91.247.240)  144.397 ms  145.382 ms  146.875 ms
11  prs-b4-link.telia.net (213.248.65.226)  148.618 ms  151.086 ms  129.073 ms


Looks like te2-2.mpd01.lon01.atlas.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

sof2er

#8
Oct 12, 2010, 07:57:47
G:\Users\Sof2er>tracert 213.248.65.226

Tracing route to prs-b4-link.telia.net [213.248.65.226]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    19 ms    19 ms    19 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    19 ms    19 ms    19 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    20 ms    19 ms    20 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
  5    19 ms    19 ms    20 ms  te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
  6    19 ms    20 ms    20 ms  te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
  7     *       51 ms   146 ms  te1-7.mpd01.lon01.atlas.cogentco.com [130.117.2.25]
  8    20 ms    19 ms    20 ms  ldn-b4-link.telia.net [213.248.70.237]
  9    20 ms    83 ms   101 ms  ldn-bb2-link.telia.net [80.91.251.14]
10    27 ms    27 ms    27 ms  prs-bb2-link.telia.net [80.91.247.240]
11    28 ms    28 ms    27 ms  prs-b4-link.telia.net [213.248.65.226]

Trace complete.

Seems to me this issue is sorted  :thumb:

jezuk1

#9
Oct 12, 2010, 08:27:01
Tracing route to eu.logon.worldofwarcraft.com [80.239.180.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    25 ms    25 ms    25 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    25 ms    25 ms    24 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    25 ms    25 ms    25 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
  5    24 ms    25 ms    24 ms  te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
  6    26 ms    25 ms    25 ms  te8-3.ccr01.lon01.atlas.cogentco.com [130.117.0.61]
  7    26 ms    25 ms    25 ms  te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.

Nitz

#10
Oct 12, 2010, 09:38:27
Try playing with a 1602 ms ping :(

CBailey

#11
Oct 12, 2010, 09:56:13
Quote from: Nitz on Oct 12, 2010, 09:38:27
Try playing with a 1602 ms ping :(

Is it still this high today? I logged in briefly before work this morning and MS was 140, was 500-1200 last night. I was rather hoping it might have been a one night affair.

Rik

#12
Oct 12, 2010, 10:12:44
Looks OK to me:

ping 213.248.65.226

Pinging 213.248.65.226 with 32 bytes of data:

Reply from 213.248.65.226: bytes=32 time=21ms TTL=57
Reply from 213.248.65.226: bytes=32 time=20ms TTL=57
Reply from 213.248.65.226: bytes=32 time=22ms TTL=57
Reply from 213.248.65.226: bytes=32 time=23ms TTL=57

Ping statistics for 213.248.65.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 23ms, Average = 21ms

tracert 213.248.65.226

Tracing route to prs-b4-link.telia.net [213.248.65.226]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.1.254
  2    14 ms    13 ms    11 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    12 ms    11 ms    13 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    14 ms    15 ms    15 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
  5    13 ms    13 ms    11 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
  6    12 ms    11 ms    13 ms  te4-3.ccr01.lon01.atlas.cogentco.com [130.117.1.217]
  7    14 ms    15 ms     *     te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
  8    15 ms    11 ms    15 ms  ldn-b4-link.telia.net [213.248.70.237]
  9    13 ms    13 ms    11 ms  ldn-bb2-link.telia.net [80.91.250.238]
10    20 ms    19 ms    21 ms  prs-bb2-link.telia.net [80.91.247.240]
11    21 ms    21 ms    23 ms  prs-b4-link.telia.net [213.248.65.226]

Trace complete.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

esh

#13
Oct 12, 2010, 16:41:28
Rik, can confirm it is fixed again at the time I wrote this.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

zappaDPJ

#14
Oct 12, 2010, 16:42:07
It was OK earlier on today for me.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#15
Oct 12, 2010, 17:01:24
 :thumb:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

#16
Oct 12, 2010, 21:11:10 Last Edit: Oct 12, 2010, 21:19:27 by gyruss
Peak time test for europe wow servers:

C:\Users\Jase>ping 213.248.65.226

Pinging 213.248.65.226 with 32 bytes of data:
Reply from 213.248.65.226: bytes=32 time=43ms TTL=57
Reply from 213.248.65.226: bytes=32 time=43ms TTL=57
Reply from 213.248.65.226: bytes=32 time=43ms TTL=57
Reply from 213.248.65.226: bytes=32 time=51ms TTL=57

Ping statistics for 213.248.65.226:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 43ms, Maximum = 51ms, Average = 45ms

C:\Users\Jase>tracert 213.248.65.226

Tracing route to prs-b4-link.telia.net [213.248.65.226]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    39 ms    35 ms    36 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    35 ms    35 ms    35 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
 4    36 ms    35 ms    35 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
 5    35 ms    35 ms    35 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
 6    35 ms    35 ms    35 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.18]
 7    36 ms    36 ms    36 ms  vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2.17]
 8    36 ms    35 ms    35 ms  ldn-b4-link.telia.net [213.248.70.237]
 9    36 ms    35 ms    61 ms  ldn-bb2-link.telia.net [80.91.250.238]
10    43 ms    58 ms    50 ms  prs-bb2-link.telia.net [80.91.247.240]
11    44 ms    43 ms    43 ms  prs-b4-link.telia.net [213.248.65.226]

Trace complete.

:thumb: :thumb: :thumb: :thumb: :thumb: :thumb:

Jase

zappaDPJ

#17
Oct 16, 2010, 17:59:24 Last Edit: Oct 16, 2010, 18:17:40 by zappaDPJ
I don't know about anyone else but since this last latency issue my in-game latency monitor is giving me consistently better results than I've ever had before with IDNet. It's been particularly low for the last 24 hours even in populated areas on highly populated realms. It seems to me something has changed but the routing looks the same.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

#18
Oct 16, 2010, 18:00:59
New routers or upgraded connections somewhere Zap?

zappaDPJ

#19
Oct 16, 2010, 18:18:36
I don't know but whatever it is I hope no one goes and breaks it again :D
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

#20
Oct 16, 2010, 18:25:39
I would suspect higher bandiwidth links have been added in the chain

Steve

#21
Oct 16, 2010, 18:43:10
It's either that or they're "robbing Peter to pay Paul"
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.
Print
Go Up Pages1
User actions