Slow Performance, Some Websites, WoW

[Ignitionnet]

I've reported this to tech support via the newsgroups, there seem to be some issues with performance on the VM <> Telia Interconnect.

As per subject:

7 7 ms 7 ms 23 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
8 47 ms 48 ms 47 ms ldn-b2-link.telia.net [213.248.100.97]
9 50 ms 65 ms 50 ms ldn-bb1-link.telia.net [80.91.251.166]
10 48 ms 47 ms 47 ms ldn-b1-link.telia.net [80.91.248.89]
11 52 ms 55 ms 76 ms 80.239.193.142
12 49 ms 49 ms 50 ms vl23.thn-gw2.plus.net [212.159.4.20]
13 52 ms 50 ms 51 ms thn1-gi0-2.namesco.net [212.159.2.10]
14 49 ms 51 ms 47 ms thn2-gi0-1.namesco.net [195.7.224.254]
15 51 ms 47 ms 47 ms the1-gi0-1.namesco.net [195.7.224.242]
16 50 ms 47 ms 47 ms gonzales.namesco.net [85.233.160.167]

Speed test to the node using that link (http://www.speedtest.bbmax.co.uk): Download Speed: 6186 kbps (773.3 KB/sec ) Upload Speed: 1589 kbps (198.6 KB/sec )

Please could you look into this, it will also be affecting World Of Warcraft, and there seem to be some routing issues on the network anyway, seems a strange aversion to routing traffic through Poplar at the moment?

Boldened part of the traceroute is the big issue, if you have both of these nodes in a traceroute to a site you will probably be seeing substandard performance.

You'll see higher than normal latency to World of Warcraft, and the London speedtest.net server and bbmax.co.uk speed testers will be slow.

I'll update when the newsgroup guys update me.

---------- Post added at 18:56 ---------- Previous post was at 17:32 ----------

Its now with networks on ref 1090571

---------- Post added at 20:36 ---------- Previous post was at 18:56 ----------

Fixed:

7 7 ms 7 ms 7 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
8 66 ms 7 ms 7 ms ldn-b2-link.telia.net [213.248.100.97]
9 6 ms 9 ms 6 ms ldn-bb1-link.telia.net [80.91.247.24]
10 16 ms 15 ms 15 ms prs-bb1-link.telia.net [80.91.247.6]

[pabscars]

How do issues like this get resolved BBd, easy on the shotgun and shovel, only I was recently asked by VM support to run traceroutes, only to be told that they look fine.

To us mere mortals that just use their broadband for entertainment, I don't understand why your first traceroute indicated a problem in the first place.

I,m being lazy I know, but your responce may help others like me who know naff all about this.

Am i correct in assuming a traceroute indicates the real path your route is taking to reach its destination. So if there is a bottle neck at a given point what can be done about it.

Ive given up trying to sort my issues and just living with whatever I get till my contract expires, but I,m still curious as to how you interpret them

[MadK9]

Fixed?

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 11 ms 11 ms sotn-cmts-08-lback-20.network.virginmedia.net [8
0.3.190.1]
3 11 ms 11 ms 12 ms sotn-t3core-1a-ge-400-1597.network.virginmedia.n
et [80.4.225.57]
4 13 ms 11 ms 11 ms win-bb-a-ge-300-0.network.virginmedia.net [62.25
3.185.49]
5 70 ms 12 ms 63 ms bre-bb-b-as5-0.network.virginmedia.net [213.105.
172.234]
6 15 ms 15 ms 15 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.
185.74]
7 1287 ms 108 ms 22 ms ldn-b2-link.telia.net [213.248.100.97]
8 13 ms 16 ms 14 ms ldn-bb2-link.telia.net [80.91.249.177]
9 22 ms 19 ms 19 ms prs-bb2-link.telia.net [80.91.254.211]
10 23 ms 22 ms 27 ms prs-b1-link.telia.net [80.91.250.249]
11 21 ms 23 ms 19 ms prs-tc-i1-link-telia.net [80.91.250.30]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.


Never used to have probs playing wow, but these last few weeks, in game MS has been terrible. I even re-installed my os, updated all drivers and such as i thought it could be a problem my end.

[Ignitionnet]

Those look largely fine sir, and from my tests earlier I couldn't see anything obvious.

That said your 2nd hop is a bit high at 11ms, I see between 5 and 7 usually.

If you're on 50Mbit could you get me the 'Upstream Burst' section from your modem?

Cheers.

EDIT: Link itself is fine, they were probably ramming more traffic than normal through it yesterday as there were routing issues:

traceroute to 213.248.100.98 (213.248.100.98), 30 hops max, 40 byte packets
1 ldn-bb2-link.telia.net (80.91.250.238) 0.443 ms ldn-bb1-link.telia.net (80.91.251.18) 0.408 ms ldn-bb2-link.telia.net (80.91.249.133) 0.414 ms
2 ldn-b3-link.telia.net (80.91.251.237) 0.564 ms ldn-b3-link.telia.net (80.91.247.25) 18.286 ms ldn-b3-link.telia.net (80.91.249.170) 0.449 ms
3 ntl-117885-ldn-b2.c.telia.net (213.248.100.98) 0.721 ms 0.745 ms 0.661 ms

[Druchii]

How do issues like this get resolved BBd, easy on the shotgun and shovel, only I was recently asked by VM support to run traceroutes, only to be told that they look fine.

To us mere mortals that just use their broadband for entertainment, I don't understand why your first traceroute indicated a problem in the first place.

I,m being lazy I know, but your responce may help others like me who know naff all about this.

Am i correct in assuming a traceroute indicates the real path your route is taking to reach its destination. So if there is a bottle neck at a given point what can be done about it.

Ive given up trying to sort my issues and just living with whatever I get till my contract expires, but I,m still curious as to how you interpret them

Bolded part is spot on.
Essentially his first traceroute showed 47ms of latency, wheras this is normally sub-10ms.
This slows down communications with the outside world, even more so with it being the second hop (One you're more likely to take more often, than say the 12th hop).

[pabscars]

Bolded part is spot on.
Essentially his first traceroute showed 47ms of latency, wheras this is normally sub-10ms.
This slows down communications with the outside world, even more so with it being the second hop (One you're more likely to take more often, than say the 12th hop).

Cheers Druchii, but what is done to rectify it, in laymans terms if poss.

[Ignitionnet]

Cheers Druchii, but what is done to rectify it, in laymans terms if poss.

Ensuring that the link isn't overloaded sorted it in this case.

[Ignitionnet]

It's back.

7 12 ms 9 ms 7 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
8 39 ms 38 ms 39 ms ldn-b2-link.telia.net [213.248.100.97]

[SnoopZ]

My internet is virtually unusable on most sites tonight, it's taking minutes to load pages if they load at all and this site is slowwwwwwwwwww, i'm in Cambridge CB24.

[edit]

Everything is ok again for now.....

[D_Skids]

I have been having the same issues in Northampton NN3. Its been off and on for a while now and is really annoying. They will just blame my kit if I report it even if I tell them if its my kit how come it suddenly works again when I haven't changed anything!

[Toto]

Would love to see some traceroutes from non VM networks to compare.

[Ignitionnet]

Would love to see some traceroutes from non VM networks to compare.

Hey Toto.

The issue arises on the transit link between VM and Telia, what would traceroutes from other networks show?

If you're interested go to http://lg.telia.net to check out Telia's network. The issue is without a doubt the link between the two, the Telia node and the VM node both show normal responses from their own networks, just as soon as you go across the link in between things go pearshaped.