London Ping times

[Dan]

Hi Guys,

I was wondering if you guys could do me a favour and ping an IP for me. It and many similar servers are located in London but for some reason I seem to be getting high pings from it.

They are all CS servers and noone else that was on the server suffered from the same problem I did and I certainly dont have problems with other servers in london I was wondering if it was a routing issue ? I normally get pings of around 35.

217.163.10.182

C:\Users\>tracert 217.163.10.182

Tracing route to 217.163.10.182 over a maximum of 30 hops

1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 34 ms 34 ms 33 ms nutmeg.dsl.enta.net [87.127.229.98]
3 34 ms 33 ms 34 ms thc1h.gi2-6.telehouse-east.dsl.enta.net [87.127.
229.78]
4 33 ms 34 ms 33 ms te5-2.telehouse-east.core.enta.net [62.249.192.1
21]
5 34 ms 33 ms 34 ms 197.g6-0.mpr2.lhr1.uk.above.net [213.161.78.221]

6 192 ms * * abv-l3-pni.London1.Level3.net [208.185.188.186]

7 64 ms 64 ms 65 ms ge-11-2.ipcolo2.London1.Level3.net [4.68.116.170
]
8 90 ms 88 ms 89 ms 217.163.10.182

Trace complete.

Looking at the trace route you can see its timing out on hop 6

6 192 ms * * abv-l3-pni.London1.Level3.net [208.185.188.186]

The the last hop is not always as bad as 89 but if it times out anywhere it seems to be on that node.

Pinging that node shows slightly higher ping times

Reply from 208.185.188.186: bytes=32 time=39ms TTL=246
Reply from 208.185.188.186: bytes=32 time=41ms TTL=246
Reply from 208.185.188.186: bytes=32 time=44ms TTL=246
Reply from 208.185.188.186: bytes=32 time=43ms TTL=246
Reply from 208.185.188.186: bytes=32 time=49ms TTL=246
Reply from 208.185.188.186: bytes=32 time=45ms TTL=246
Reply from 208.185.188.186: bytes=32 time=42ms TTL=246
Reply from 208.185.188.186: bytes=32 time=41ms TTL=246
Reply from 208.185.188.186: bytes=32 time=43ms TTL=246
Reply from 208.185.188.186: bytes=32 time=48ms TTL=246
Reply from 208.185.188.186: bytes=32 time=44ms TTL=246
Reply from 208.185.188.186: bytes=32 time=46ms TTL=246
Reply from 208.185.188.186: bytes=32 time=45ms TTL=246
Reply from 208.185.188.186: bytes=32 time=47ms TTL=246
Reply from 208.185.188.186: bytes=32 time=44ms TTL=246
Reply from 208.185.188.186: bytes=32 time=45ms TTL=246
Reply from 208.185.188.186: bytes=32 time=39ms TTL=246
Reply from 208.185.188.186: bytes=32 time=42ms TTL=246
Reply from 208.185.188.186: bytes=32 time=131ms TTL=246
Request timed out.

I seem to get time outs every minute or so. Just wondering what could be causing this as others don't seem to be experiencing it.

Another odd thing is if you run a whois against that IP (208.185.188.186)

You get this :-

OrgName: Abovenet Communications, Inc
OrgID: ABVE
Address: 360 Hamilton Ave
City: White Plains
StateProv: NY <-----------
PostalCode: 10601
Country: US <-------------

Going that the router has "London" in the name.....

[James]

It may be that they own the line over here, but as they are physically based in the US that's just their company address. So in theory the router/pipe could well be over here.

What's the traceroute like now - any better? Might have just been a routing issue as you say.

Here's a traceroute from an off-site Be* connection, but one that's closer to that particular server so missed out most of the routers

Tracing route to 217.163.10.182 over a maximum of 30 hops

1 65 ms 99 ms 99 ms x.x.x.x
2 * * * Request timed out.
3 13 ms 13 ms * 195.50.118.225
4 13 ms 13 ms 14 ms ge-10-0.ipcolo2.London1.Level3.net [4.68.116.10]
5 13 ms 13 ms 13 ms 217.163.10.182

[Dan]

Tracing route to 217.163.10.182 over a maximum of 30 hops

1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 33 ms 34 ms 34 ms nutmeg.dsl.enta.net [87.127.229.98]
3 33 ms 34 ms 34 ms thc1h.gi2-6.telehouse-east.dsl.enta.net [87.127.
229.78]
4 222 ms 115 ms 34 ms te5-2.telehouse-east.core.enta.net [62.249.192.1
21]
5 33 ms 33 ms 34 ms 197.g6-0.mpr2.lhr1.uk.above.net [213.161.78.221]

6 34 ms 33 ms * abv-l3-pni.London1.Level3.net [208.185.188.186]

7 34 ms 34 ms 34 ms ge-11-2.ipcolo2.London1.Level3.net [4.68.116.170
]
8 35 ms 34 ms 34 ms 217.163.10.182

Trace complete.

Pinging 217.163.10.182 with 32 bytes of data:

Reply from 217.163.10.182: bytes=32 time=34ms TTL=53
Reply from 217.163.10.182: bytes=32 time=32ms TTL=53
Reply from 217.163.10.182: bytes=32 time=77ms TTL=53
Reply from 217.163.10.182: bytes=32 time=33ms TTL=53

Ping statistics for 217.163.10.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 77ms, Average = 44ms

Just read about someone else having Interleaving turned off and it improved their pings by quite a bit could I be a pain in the arse and request that it be turned off. If my connection becomes unstable we might have to turn it back on again but it would be interesting to see what difference it makes to my CS scores ;)

[James]

Hi Dan. This will be off within 24hrs :)

James

[Dan]

Thankyou :)

[Paul_ADSL24]

Abovenet are one of the international carriers so will have equipment all over the world

[Dan]

Ive had a couple of emails back from abovenet regarding the issues with that router that was causing packet loss

"You should send this to Level 3.At hop 6 of your trace the data does not have to come back through us. There is nothing wrong with our network or routers at this time."

So even though that routers IP is registered to abovenet it appears they seem to think that its level 3's responsibility ?!

So Im trying to find some details for level 3 so I can email them.

[Dan]

Is it possible to setup a static route to bypass these horrible level 3 servers ? Either by adding one to my router or from your end ? Or possibly they might be more responsive if a ISP contacted them ??