Has IDNet always routed through enta.net?

juiceuk · Apr 14, 2009, 04:52:26

Hi, this has been bugging me since around the time when the pipes got fixed. I play battlefield 2142 in a clan and have not been able to play too well thanks to the fact that the people I'm trying to shoot are warping from one spot to the next or it just does not register the hits I make. My new computer can handle this game on high settings with ease so its not graphics related. I tried on my other computer too and the same thing happens. I check my ping in game when it happens and it alway stays in a range of 22 to 26 normally just stays rock steady. I thought maybe packet loss or something because the ping looks low when I check ingame so I ran pingplotter to some servers I play on for awhile and no packet loss but it shows big ping spikes when it hits enta.net ip's. I presume they are my problem with regular ping spikes as soon as it hits them. Any thoughts? Have we always routed through enta.net? I am one of the better players and nothing bugs me more than people knifing me or out shooting me that I would normal wipe the floor with and costing us the match.

Target Name: N/A
IP: 193.93.46.71
Date/Time: 14/04/2009 03:30:44 to 14/04/2009 04:08:58

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 459 0 0.0 2 7 2 [192.168.1.1]
2 459 0 0.0 22 1187 27 telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 459 0 0.0 22 279 25 telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 459 0 0.0 22 239 40 lonap2.enta.net [193.203.5.135]
5 459 0 0.0 22 185 26 te4-4.telehouse-east.core.enta.net [87.127.236.97]
6 459 0 0.0 22 210 28 te2-3.redbus-sov3.core.enta.net [87.127.236.29]
7 459 0 0.0 22 230 37 84-45-244-174.static.enta.net [84.45.244.174]
8 459 0 0.0 22 33 23 [193.93.46.71]

One second it does this.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>tracert 193.93.46.71

Tracing route to 193.93.46.71 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.1.1
2 25 ms 24 ms 24 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 23 ms 24 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 24 ms 24 ms 30 ms lonap2.enta.net [193.203.5.135]
5 225 ms 245 ms 40 ms te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
6 24 ms 28 ms 24 ms te2-3.redbus-sov3.core.enta.net [87.127.236.29]

7 211 ms 203 ms 226 ms 84-45-244-174.static.enta.net [84.45.244.174]
8 25 ms 24 ms 24 ms 193.93.46.71

Trace complete.

Next second it like this

Tracing route to 193.93.46.71 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.1.1
2 23 ms 24 ms 24 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 23 ms 25 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 25 ms 24 ms 25 ms lonap2.enta.net [193.203.5.135]
5 25 ms 25 ms 24 ms te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
6 24 ms 24 ms 24 ms te2-3.redbus-sov3.core.enta.net [87.127.236.29]

7 24 ms 24 ms 24 ms 84-45-244-174.static.enta.net [84.45.244.174]
8 24 ms 25 ms 26 ms 193.93.46.71

Trace complete.

I thought I would just wait it out and it would go away but it has not.

Rik · Apr 14, 2009, 08:19:57

You need to talk to support on this, Juice, we're not privy to particular peering/routing arrangements. Fwiw, I get:

tracert 193.93.46.71

Tracing route to 193.93.46.71 over a maximum of 30 hops

1 1 ms <1 ms 1 ms home [192.168.1.254]
2 22 ms 21 ms 23 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 21 ms 21 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 21 ms 21 ms 21 ms lonap2.enta.net [193.203.5.135]
5 24 ms 21 ms 21 ms te4-4.telehouse-east.core.enta.net [87.127.236.97]
6 22 ms 21 ms 23 ms te2-3.redbus-sov3.core.enta.net [87.127.236.29]
7 22 ms 21 ms 21 ms 84-45-244-174.static.enta.net [84.45.244.174]
8 26 ms 23 ms 21 ms 193.93.46.71

Trace complete.

Sebby · Apr 14, 2009, 13:11:50

Could it be that the site is hosted by Enta?

Rik · Apr 14, 2009, 15:04:16

It has the feel doesn't it, Seb.

kinmel · Apr 14, 2009, 15:23:23

It is hosted on www.rackage.com and their announcements page warned of interruptions to virtual game servers due to planned maintenance at their Level(3), Braham St, Facility.

Rik · Apr 14, 2009, 15:27:02

Thanks, Alan.

juiceuk · Apr 14, 2009, 15:32:19

I will give support a call. Check this quick 50 samples I done to a another server I play on. Packet loss, high ping you name it I got it!

Target Name: server.killercreation.co.uk
IP: 81.19.209.167
Date/Time: 14/04/2009 14:50:44 to 14/04/2009 14:55:37

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 50 0 0.0 2 3 2 [192.168.1.1]
2 50 0 0.0 22 169 69 telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 50 1 2.0 22 323 75 telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 50 1 2.0 22 202 77 lonap2.enta.net [193.203.5.135]
5 50 0 0.0 22 178 73 te4-1.telehouse-north.core.enta.net [87.127.236.38]
6 50 1 2.0 22 152 66 Transit-enta.KillerCreation.co.uk [62.249.255.186]
7 50 0 0.0 23 159 65 server.killercreation.co.uk [81.19.209.167]

Thought I would try doing another 50 samples to 193.93.46.71 to compare.

Target Name: N/A
IP: 193.93.46.71
Date/Time: 14/04/2009 15:11:49 to 14/04/2009 15:19:59

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 50 0 0.0 2 6 2 [192.168.1.1]
2 50 0 0.0 22 251 49 telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 50 1 2.0 22 123 43 telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 50 0 0.0 22 240 48 lonap2.enta.net [193.203.5.135]
5 50 0 0.0 23 257 45 te4-4.telehouse-east.core.enta.net [87.127.236.97]
6 50 0 0.0 22 214 47 te2-3.redbus-sov3.core.enta.net [87.127.236.29]
7 50 0 0.0 23 219 46 84-45-244-174.static.enta.net [84.45.244.174]
8 50 0 0.0 22 143 35 [193.93.46.71]

Even IDNet looking bad on those ones. Rick does yours always stay at low 20's? Could someone do 50 samples with pingplotter to either address I've used?

Rik · Apr 14, 2009, 15:34:44

I don't use Ping Plotter, but I've got PingGraph running and will post back results later. Currently, I'm showing 21-34ms.

Rik · Apr 14, 2009, 15:50:43

Here's some 15 minutes to the second site, or 150 pings, 10-34ms with an average of just over 22ms.

[attachment deleted by admin]

Rik · Apr 14, 2009, 16:08:43

This is your first server, 19-29ms with one spike of 276ms.

[attachment deleted by admin]

juiceuk · Apr 14, 2009, 16:22:54

Kinmel did you mean this?

Planned Maintenance - 19th April - Datacenter 5yr UPS Maintenance - 15-03-2008, 03:22 PM

--------------------------------------------------------------------------------

There are going to be 3 planned maintenance windows effecting some of our servers.

19th April - Affecting Level(3) Braham St Facility - More details to follow.

Thats all I could find on rackage.com about maintenance and it's dated 2008.

Rick , Thanks for that. I used ping plotter because it shows what a tracert shows. If I use the round trip time it says what the ingame ping says and thats a low ping. Something is happening on the way to the IP that does not show up in the end round trip time.

Rik · Apr 14, 2009, 16:41:29

I really think you need to talk to IDNet, I have limited diagnostics available to me.

juiceuk · Apr 14, 2009, 16:44:54

I've contacted IDNet and have to send them the data I collected. Lets hope they find the problem?

zappaDPJ · Apr 14, 2009, 16:54:01

Pings and a tracert to the first IP are rock solid for me. I think only IDNet support can give you answers I'm afraid. Good luck!

QuoteMicrosoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>ping 81.19.209.167 -n 50

Pinging 81.19.209.167 with 32 bytes of data:
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=23ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=26ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=26ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=23ms TTL=122
Reply from 81.19.209.167: bytes=32 time=25ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=26ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=23ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=26ms TTL=122
Reply from 81.19.209.167: bytes=32 time=24ms TTL=122
Reply from 81.19.209.167: bytes=32 time=26ms TTL=122

Ping statistics for 81.19.209.167:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 26ms, Average = 24ms

C:\Users\zappaDPJ>tracert 81.19.209.167

Tracing route to server.killercreation.co.uk [81.19.209.167]
over a maximum of 30 hops:

1 2 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 27 ms 24 ms 25 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 24 ms 25 ms 24 ms lonap2.enta.net [193.203.5.135]
5 24 ms 27 ms 25 ms te4-1.telehouse-north.core.enta.net [87.127.236.
38]
6 26 ms 25 ms 25 ms Transit-enta.KillerCreation.co.uk [62.249.255.18
6]
7 25 ms 25 ms 24 ms server.killercreation.co.uk [81.19.209.167]

Trace complete.

C:\Users\zappaDPJ>

Rik · Apr 14, 2009, 16:58:18

Thanks, Zappa.

kinmel · Apr 14, 2009, 18:22:55

Quote from: juiceuk on Apr 14, 2009, 16:22:54
Kinmel did you mean this?

Planned Maintenance - 19th April - Datacenter 5yr UPS Maintenance - 15-03-2008, 03:22 PM

--------------------------------------------------------------------------------

There are going to be 3 planned maintenance windows effecting some of our servers.

19th April - Affecting Level(3) Braham St Facility - More details to follow.

Thats all I could find on rackage.com about maintenance and it's dated 2008.

Yes, i was merely pointing out where some of their servers are located, they also appear to have some at Redbus with Tiscali

Colin Burns · Apr 14, 2009, 21:03:44

Dang why ive been noticing the inconsistencies for a while but always just assumed because it was because i was downloading large files when i was checking routing but the blip is deffinetly a pain

colin@colin-desktop:~$ traceroute jndhost.net
traceroute to jndhost.net (94.76.229.217), 30 hops max, 40 byte packets
1 home (192.168.1.254) 3.138 ms 3.167 ms 3.179 ms
2 telehouse-gw2-lo2.idnet.net (212.69.63.55) 91.211 ms 91.192 ms 95.581 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 53.597 ms 53.600 ms 57.622 ms
4 lonap2.enta.net (193.203.5.135) 57.616 ms 57.601 ms *
5 te4-4.telehouse-east.core.enta.net (87.127.236.97) 57.553 ms 59.871 ms 61.394 ms
6 78-33-51-146.static.enta.net (78.33.51.146) 65.913 ms 33.883 ms 37.090 ms
7 pri.hex-the.as29550.net (92.48.95.9) 53.260 ms 41.947 ms 43.271 ms
8 bac.bsq3-hex.as29550.net (217.112.81.94) 58.068 ms 57.966 ms 57.935 ms
9 server.jndhostns.net (94.76.229.217) 56.013 ms 56.003 ms 57.833 ms
colin@colin-desktop:~$

and then

traceroute to jndhost.net (94.76.229.217), 30 hops max, 40 byte packets
1 home (192.168.1.254) 0.700 ms 0.725 ms 2.243 ms
2 telehouse-gw2-lo2.idnet.net (212.69.63.55) 33.370 ms 35.311 ms 37.161 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 36.896 ms 36.050 ms 35.932 ms
4 lonap2.enta.net (193.203.5.135) 37.241 ms 37.139 ms 37.028 ms
5 te4-4.telehouse-east.core.enta.net (87.127.236.97) 139.264 ms 139.179 ms 139.051 ms
6 78-33-51-146.static.enta.net (78.33.51.146) 42.107 ms 30.617 ms 34.486 ms
7 pri.hex-the.as29550.net (92.48.95.9) 34.871 ms 32.457 ms 31.005 ms
8 bac.bsq3-hex.as29550.net (217.112.81.94) 36.756 ms 40.339 ms 40.321 ms
9 server.jndhostns.net (94.76.229.217) 39.400 ms