Lag :/

Desaan · Apr 26, 2008, 16:10:45

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 30 ms 34 ms 24 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
2 23 ms 30 ms 30 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

3 97 ms 219 ms 320 ms y-s-2.lon1.arbinet.net [213.232.64.76]
4 30 ms 30 ms 29 ms ae-12-55.car2.London1.Level3.net [4.68.116.144]

5 26 ms 30 ms 29 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
6 27 ms 30 ms 30 ms ldn-bb1-link.telia.net [80.91.249.77]
7 39 ms 39 ms 40 ms prs-bb1-pos6-0-0.telia.net [213.248.64.9]
8 36 ms 39 ms 40 ms prs-b1-link.telia.net [80.91.250.249]
9 38 ms 39 ms 39 ms prs-tc-i1-link-telia.net [80.91.250.30]

Node 3 has been killing me for weeks, who owns this? Any ideas?

Rik · Apr 26, 2008, 16:16:57

http://www.arbinet.com/

Mine doesn't seem so bad:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS>tracert host-81.wow-europe.com
Unable to resolve target system name host-81.wow-europe.com.

tracert 80.239.179.81

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 27 ms 23 ms 23 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 27 ms 23 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 151 ms 216 ms 200 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 26 ms 23 ms 23 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]
6 29 ms 23 ms 33 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
7 23 ms 23 ms 25 ms ldn-bb2-link.telia.net [80.91.251.14]
8 67 ms 64 ms 64 ms prs-bb1-pos6-0-0.telia.net [213.248.64.9]
9 66 ms 64 ms 62 ms prs-b1-link.telia.net [80.91.250.249]
10 35 ms 31 ms 35 ms prs-tc-i1-link-telia.net [80.91.250.30]

I'd suggest you do a range of tracerts across different times of the day and then drop support an email with the results. They may be able to re-route the traffic.

Desaan · Apr 26, 2008, 16:22:30

Arbinet support or Idnet?

sobranie · Apr 26, 2008, 16:22:59

Who Is on arbin net here;

http://www.whois.ws/whois-net/ip-address/arbin.net/

None the wiser really!!

Rik · Apr 26, 2008, 16:23:23

IDNet, support@idnet.net. Arbinet are unlikely to talk to you as you're not their customer.

Rik · Apr 26, 2008, 16:24:25

Quote from: sobranie on Apr 26, 2008, 16:22:59
Who Is on arbin net here;

http://www.whois.ws/whois-net/ip-address/arbin.net/

None the wiser really!!

Strange that they're using a GMail contact address.

Desaan · Apr 26, 2008, 16:29:23

I wouldn't be exaggerating if I said it's been like this for a LONG time, I stopped playing Warcraft a while ago soley because the latency to this node was ridiculously high most times of the day. I'll definitely be sending a support email, I've had enough of these clowns

Sebby · Apr 26, 2008, 17:20:58

It's definitely worth contacting IDNet in that case. If the problem isn't at their end, they'll do their best to get to the bottom of it, I'm sure.

RA-1972 · Apr 26, 2008, 18:55:53

Mine seems good . No 4.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\tracert 80.239.179.81

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms local.gateway [10.0.0.2]
2 19 ms 17 ms 18 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 19 ms 21 ms 17 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 22 ms 18 ms 18 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 19 ms 19 ms 21 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]

6 18 ms 24 ms 36 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 19 ms 23 ms 18 ms ldn-bb2-link.telia.net [80.91.251.14]
8 60 ms 59 ms 61 ms prs-bb2-pos6-0-0.telia.net [213.248.65.114]
9 59 ms 64 ms 60 ms prs-b1-link.telia.net [80.91.250.253]
10 28 ms 28 ms 28 ms prs-tc-i1-link-telia.net [80.91.250.30]
11 * * * Request timed out.
12 * *

Rik · Apr 26, 2008, 18:57:49

Mine too now:

tracert 80.239.179.81

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms home [192.168.1.254]
2 24 ms 23 ms 25 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 23 ms 23 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 62 ms 43 ms 29 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 27 ms 25 ms 23 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]
6 27 ms 25 ms 23 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
7 23 ms 25 ms 25 ms ldn-bb2-link.telia.net [80.91.250.238]
8 62 ms 63 ms 62 ms prs-bb2-link.telia.net [80.91.254.211]
9 67 ms 66 ms 62 ms prs-b1-link.telia.net [80.91.250.249]
10 32 ms 32 ms 33 ms prs-tc-i1-link-telia.net [80.91.250.30]

Desaan · Apr 27, 2008, 03:43:47

I think part of the problem for me is it's very unstable. It's fine one minute then horrendous the next, and there is nothing I can do about it. Like today, 300+ms for a few hours, then came back down around 6-7pm then shot up again about 9pm to the way it was earlier.

Shoddy performance

Sebby · Apr 27, 2008, 12:48:59

Quote from: Desaan on Apr 27, 2008, 03:43:47
Shoddy performance

Agreed, but not necessarily on IDNet's part. We all know that there is a lot of BT maintenance going on at the moment. Have you sent support an email? Unfortunately, complaining here won't resolve the issue. We are just an unofficial forum; problems must be directed at IDNet.

Ham · Apr 28, 2008, 19:55:29

this lag probs has started over past few weeks since idnet done some upgrades or something
my online game play is suffering terrible at the moment

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Hammy>tracert 80.239.179.81

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 49 ms 48 ms 48 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 48 ms 46 ms 47 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 50 ms 46 ms 49 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 * 47 ms 49 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]

6 49 ms 50 ms 48 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 47 ms 51 ms 53 ms ldn-bb2-link.telia.net [80.91.250.238]
8 118 ms 121 ms 118 ms prs-bb1-pos6-0-0.telia.net [213.248.64.9]
9 118 ms 120 ms 118 ms prs-b1-link.telia.net [80.91.250.249]
10 56 ms 57 ms 57 ms prs-tc-i1-link-telia.net [80.91.250.30]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15

Rik · Apr 28, 2008, 19:56:18

Have you contacted support?

RA-1972 · Apr 28, 2008, 20:03:06

try reconnecting ur ppp session that helped mine down in the teens now . Bt done some work the other day down my way and my pings jump up to the 40 , done a couple reconnects with ppp session and all good again now . Hope it helps .

RA-1972 · Apr 28, 2008, 20:04:29

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\>tracert 80.239.179.81

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms local.gateway [10.0.0.2]
2 19 ms 20 ms 18 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 18 ms 18 ms 19 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 20 ms 19 ms 22 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 19 ms 18 ms 18 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]

6 19 ms 19 ms 19 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 18 ms 24 ms 20 ms ldn-bb1-link.telia.net [80.91.251.18]
8 * 93 ms 76 ms prs-bb2-pos6-0-0.telia.net [213.248.65.114]
9 78 ms 75 ms 76 ms prs-b1-link.telia.net [80.91.250.253]
10 28 ms 32 ms 31 ms prs-tc-i1-link-telia.net [80.91.250.30]
11 * * * Request timed out.
12

Ham · Apr 28, 2008, 20:37:30

i have called support and emails them random tracerts ect
still no fix to the problem looking like a migration soon tbh

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Hammy>tracert 80.239.179.81

Tracing route to host-81.wow-europe.com [80.239.179.81]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 54 ms 46 ms 48 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 47 ms 46 ms 50 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 120 ms 234 ms 240 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 67 ms 47 ms 49 ms ae-22-56.car2.London1.Level3.net [4.68.116.176]

6 57 ms 47 ms 48 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 50 ms 60 ms 50 ms ldn-bb2-link.telia.net [80.91.250.238]
8 108 ms 110 ms 104 ms prs-bb1-pos6-0-0.telia.net [213.248.64.9]
9 101 ms 108 ms 105 ms prs-b1-link.telia.net [80.91.250.253]
10 56 ms 56 ms 57 ms prs-tc-i1-link-telia.net [80.91.250.30]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15

Sebby · Apr 28, 2008, 20:52:41

It doesn't look like it's IDNet that's the problem from that tracert... I'd send them that again, or point them at this thread.

james_idnet · Apr 29, 2008, 12:05:04

Hi All,

Ignoring the fact that this was written by an NTL customer, i think the information he provides in his explanation of his traceroute guide should help with some of what you are seeing.

http://homepage.ntlworld.com/robin.d.h.walker/cmtips/traceroute.html

Most importantly the section on "How traceroute can mislead" should explain the obscure findings in some of the traceroutes in the thread.

James (IDNet)

Rik · Apr 29, 2008, 12:06:58

Nice link, James.

Sebby · Apr 29, 2008, 13:19:43

Thanks, James.

Simon · Apr 29, 2008, 21:44:14

Ditto!