Traceroute to lazeryattack

[FireFoXx]

Hello,

Nildram ADSL seems to take a roundabout route to reach lazeryattack servers ... (not sure where those Telia routers are, but there is one router further down which seems to be in Amsterdam?).

Is this normal? ... And is a 38ms ping considered "ideal" for a UK client connecting to a UK server?

Cheers.

===============================

Tracing route to 213.230.209.100 (Savage) over a maximum of 30 hops

1 17 ms <1 ms <1 ms 192.168.1.1
2 12 ms 13 ms 12 ms lo1-lon3-adsl21.nildram.net [195.112.5.30]
3 13 ms 13 ms 12 ms lon3-14.nildram.net [84.12.224.33]
4 13 ms 12 ms 12 ms lon1-9.nildram.net [84.12.224.14]
5 13 ms 13 ms 12 ms nildram-gw.telecomplete.net [213.160.97.17]
6 13 ms 12 ms 13 ms v101-r4.thn.telecomplete.net [213.160.96.121]
7 14 ms 14 ms 14 ms lc-host.cust.telecomplete.net [213.160.97.150]
8 13 ms 13 ms 14 ms gi0-0.backbone.the.core.lchost.net [213.230.194.36]
9 14 ms 13 ms 14 ms 213.230.209.100

Trace complete.
Press any key to continue . . .

===============================

Tracing route to 81.27.73.100 (lazeryattack) over a maximum of 30 hops

1 17 ms <1 ms <1 ms 192.168.1.1
2 13 ms 12 ms 13 ms lo1-lon3-adsl21.nildram.net [195.112.5.30]
3 13 ms 12 ms 13 ms lon3-14.nildram.net [84.12.224.33]
4 13 ms 13 ms 13 ms ldn-b3-geth5-1.telia.net [213.248.100.29]
5 12 ms 12 ms 12 ms ldn-bb2-pos6-1-0.telia.net [213.248.64.49]
6 21 ms 19 ms 21 ms adm-bb2-pos6-0-0.telia.net [213.248.65.158]
7 20 ms 20 ms 20 ms adm-b1-pos4-0.telia.net [213.248.72.142]
8 20 ms 19 ms 21 ms ge-6-10.car2.Amsterdam1.Level3.net [213.244.165.249]
9 21 ms 21 ms 65 ms 4.68.96.197
10 36 ms 36 ms 37 ms as-1-0.bbr2.London1.Level3.net [212.187.128.25]
11 36 ms 36 ms 36 ms ge-7-0.ipcolo2.London1.Level3.net [212.187.131.132]
12 37 ms 37 ms 38 ms IPCUST-DHMS-HBX-A.lon.ipmh.telecity.net [217.20.34.11]
13 38 ms 39 ms 40 ms 81.27.64.7
14 37 ms 38 ms 38 ms 81.27.73.100

Trace complete.
Press any key to continue . . .

===============================

[Fyrespray]

I have had problems with the 4.68.96.197 jump before, here are the last two mails I got from the network support team that I use for connection issues:

Hi Mark,

Following on from our initial Level3 update we received the following:

The latency you are seeing is due to the fact that Telia is advertising the best available route to your destination from a public peering point on our network. We have seen a large increase in traffic destined for Telia recently, however, Telia does not have sufficient bandwidth at this peering point to handle all of the traffic they are inviting. I referred the issue to our IP NOC, and they have escalated to one of our Sr Engineers. I expect we will be contacting Telia to work out an appropriate solution.

They will keep us updated of any progress.

Kind Regards,
Andy.

Mark,

You shouldn't see this latency anymore, Level3 have informed us they stopped sending traffic over that Telia link.

Now obviously they can't control every ISP and routing issues via Telia are something that is outside of thier control. Telia has been informed (as far as i'm aware) but it would appear that they are still advertising for traffic. The issue only seems to be affecting Nildram and unfortunatly a 48 ping is not high enough for my SLA's to kick into action (Yes it is bad but not exactly unplayable). the upshoot is that this is a Nildram specific routing problem and something that Nildram needs to fix (i.e. Nildram needs to stop routing via Telia because they are asking for more bandwidth than they can handle). I have forwarded on some tracert's to my networking team but don't think they will be able to do much due to the fact that this is outside their control. The best thing you can do is phone up Nildram and moan at then and tell them to stop routing via Telia (Feel free to quote this post, the fact that Level 3 has had problems with them should count for something).

I will let you know what I get back from the networking team but as it is a Nildram specific issue I'm not expecting them to be able to do much, Nildram (Or rather thier routing via Telia) is the problem here, not me.

[FireFoXx]

Thanks Fyrespray,

I'll be contacting Nildram about the problem in the next couple of days ... Will let you know what happens after that.

[Fyrespray]

Update from my networking team:

Hi Mark,

We're still awaiting on a reply from Level3 with regards to the Nildram
routing, hopefully they can shed some information on their peerings with
Telia.

I did check Nildram's routing from their Looking Glass:
http://www.nildram.net/traceroute.cgi?81.27.73.100

Result for 81.27.73.100:

traceroute to 81.27.73.100 (81.27.73.100), 30 hops max, 40 byte packets
1 lon1-9 (195.149.20.130) 0.357 ms 0.290 ms 0.248 ms
2 246.ge5-0.mpr1.lhr1.uk.above.net (213.161.78.49) 0.226 ms 0.166 ms
0.167 ms
3 pos4-0.mpr2.lhr1.uk.above.net (208.185.156.14) 0.307 ms 0.197 ms
0.174 ms
4 pos2-2.core1.London1.Level3.net (208.185.188.186) 0.647 ms 1.391
ms 1.157 ms
5 ge-7-0.ipcolo2.London1.Level3.net (212.187.131.132) 1.148 ms 0.806
ms 0.640 ms
6 IPCUST-DHMS-HBX-A.lon.ipmh.telecity.net (217.20.34.11) 0.970 ms
0.835 ms 0.807 ms
7 81.27.64.7 (81.27.64.7) 2.028 ms 1.974 ms 1.594 ms
8 81.27.73.100 (81.27.73.100) 1.332 ms 1.510 ms 1.132 ms

That seems to go via AboveNet right now - not sure if Telia or Level3
have acted on any of the routing issues though to change this.

As soon as I hear from Level3 i'll let you know.

Andy.

[Fyrespray]

All problems should have been resolved now. I am reliably informed that Nildram have pulled their finger out and sorted out thier routing (I should also point out that this was nothing to do with me, although I wish I could claim credit :) ).

Please shout if you get any more problems and I will set the networking team onto it again.