High ping on idnet?

[mrapoc]

http://www.idnetters.co.uk/forums/index.php?topic=12515.150

please post up and also give idnet support an email too

im sure as hell getting bad pings lol

Cod4 pings on our servers are 180ms ish and

C:\Users\Sam>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=124ms TTL=123

Reply from 212.69.36.86: bytes=32 time=160ms TTL=123

Reply from 212.69.36.86: bytes=32 time=139ms TTL=123

Reply from 212.69.36.86: bytes=32 time=154ms TTL=123

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 124ms, Maximum = 160ms, Average = 144ms

please post on our thread if you do have problems (and also contact support) so they can do somethin about it

btw and for a last resort, anyone have a isp recommendation?

• 1 month contract
  
• Reliable
  
• Great support
  
• Low pings/good speed
  

 

[moogle]

Those are high pings! I'm getting..

Microsoft Windows [Version 6.0.6001]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Moogle>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=14ms TTL=122

Reply from 212.69.36.86: bytes=32 time=13ms TTL=122

Reply from 212.69.36.86: bytes=32 time=14ms TTL=122

Reply from 212.69.36.86: bytes=32 time=14ms TTL=122

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 13ms, Maximum = 14ms, Average = 13ms

C:\Users\Moogle>

btw and for a last resort, anyone have a isp recommendation?

• 1 month contract
  
• Reliable
  
• Great support
  
• Low pings/good speed
  

The bit that limits you is the 1 month contract bit

If you want a 1 month contract you gotta compromise and get stuck with a limited selection of ISP's.

I'm on O2 atm and was on Be*. Paying £9~ a month because my sisters an O2 customer. Be* is way better on the pings (because you can get fastpath) but had to start saving since the recession.

Anyway O2 are good if you're willing to have a 12 month contract. With Be if you're on the Pro tier then your contract is 3 months, as in you can cancel anytime but you have to give 3 months notice.

 

[deathwish]

same here

Tracing route to idnet.net [212.69.36.10]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 341 ms 196 ms 81 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]

3 39 ms 39 ms 40 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 42 ms 42 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]

5 41 ms 39 ms 44 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]

6 42 ms 41 ms 41 ms www.idnet.net [212.69.36.10]

Trace complete.

Tracing route to www.overclock3d.net [212.69.36.86]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1

2 105 ms 256 ms 148 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]

3 111 ms 126 ms 120 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 124 ms 135 ms 145 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]

5 125 ms 131 ms 122 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]

6 121 ms 132 ms 113 ms oc2.overclock3d.net [212.69.36.86]

Trace complete.

Tracing route to www.l.google.com [66.102.9.99]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1

2 276 ms 79 ms 85 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]

3 90 ms 85 ms 108 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 106 ms 97 ms 99 ms 195.66.224.125

5 69 ms 74 ms 82 ms 209.85.252.40

6 122 ms 126 ms 119 ms 209.85.251.190

7 153 ms 146 ms 150 ms 64.233.174.187

8 151 ms 127 ms 118 ms 64.233.174.18

9 81 ms 88 ms 103 ms 66.102.9.99

Trace complete.

 

[JN]

I think that might have been a problem with our server mrapoc rather than IDNet.

After the problems we had on Sunday I rebooted our server and for some reason the network card was running at half-duplex (rather than full duplex) and subsequently everything was running like a dead dog.

I only noticed it this morning when our overnight backups that normally take 2-3hrs were taking 16+hrs :s

Should all be fine now, but I'm scraping together the funds to buy some quad-port server class network cards for the servers :yumyum:

 

[mrapoc]

Unfortunately jim i think not

C:\Users\Sam>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=189ms TTL=59

Reply from 212.69.36.10: bytes=32 time=194ms TTL=59

Reply from 212.69.36.10: bytes=32 time=191ms TTL=59

Reply from 212.69.36.10: bytes=32 time=192ms TTL=59

Ping statistics for 212.69.36.10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 189ms, Maximum = 194ms, Average = 191ms

dang

 

[FarFarAway]

Nope I have the same here too

C:\Users\Matt>ping www.google.co.uk

Pinging www.l.google.com [66.102.9.147] with 32 bytes of d

Reply from 66.102.9.147: bytes=32 time=176ms TTL=247

Reply from 66.102.9.147: bytes=32 time=172ms TTL=247

Reply from 66.102.9.147: bytes=32 time=175ms TTL=247

Reply from 66.102.9.147: bytes=32 time=173ms TTL=247

Ping statistics for 66.102.9.147:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 172ms, Maximum = 176ms, Average = 174ms

Sam have you got anything back from IDNET?

 

[deathwish]

quote from there site

Network Status

2009-02-02 17:04: Some users are still experiencing periods of higher latency (pings) than normal whilst we continue to rebalance our network following the new capacity added on Friday. Apologies to those affected, optimisation is taking a little longer than expected but we are making progress and hope to reach optimum performance within the next 24 hours.

that was yesterday

mines back to normal now

Pinging www.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=39ms TTL=123

Reply from 212.69.36.86: bytes=32 time=41ms TTL=123

Reply from 212.69.36.86: bytes=32 time=39ms TTL=123

Reply from 212.69.36.86: bytes=32 time=39ms TTL=123

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 39ms, Maximum = 41ms, Average = 39ms

 

[FarFarAway]

I usually get ~8ms to IDNET or OC3D

 

[deathwish]

I usually get ~8ms to IDNET or OC3D

with interleaving off?

my connection has it on at the moment but it will be off tomorow

 

[FarFarAway]

with interleaving off?

my connection has it on at the moment but it will be off tomorow

Yep it's off

I've got a pretty naff line, but a very good router

 

[mrapoc]

Well I jsut rang support as my "normal" ping had increased too over the past 6 months...turns out i had interleaving so the next 24 hours i should see a change there

Turns out the BT auto "balancer" for the pipelines went a bit wrong. Also a router restarted or something today meaning it took even longer to manually rectify the overbalancing issues as every1 got reconnected at once lol..

Chances are it should be fixed now/tomorrow.

Try resetting your PPP (connection to isp in your router) as this fixed my pings (for now)

Or turn router off for half an hour (if you can bare it) although the PPP reset fixed my pings back to "normal"

 

[FarFarAway]

OK I'll drop and reconnect PPoA

My router tends to hang on to a connection for it's dear life so perhaps my line could do with re-training anyway

Got it down to 16ms to idnet

EDIT: Except that one hop was 59ms

 

[Bungral]

Hmmmm not so good over here on Sky...

Could probably do with restarting my router.

Microsoft Windows [Version 6.0.6001]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Marc>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=50ms TTL=120

Reply from 212.69.36.86: bytes=32 time=54ms TTL=120

Reply from 212.69.36.86: bytes=32 time=51ms TTL=120

Reply from 212.69.36.86: bytes=32 time=51ms TTL=120

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 50ms, Maximum = 54ms, Average = 51ms

C:\Users\Marc>

 

[JN]

Any chance those with high pings still could try pinging oc1.overclock3d.net and oc2.overclock3d.net. I'm interested to see the difference

 

[Bungral]

Your wish is my cmd.... Get it?? :

Microsoft Windows [Version 6.0.6001]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Marc>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=50ms TTL=120

Reply from 212.69.36.86: bytes=32 time=54ms TTL=120

Reply from 212.69.36.86: bytes=32 time=51ms TTL=120

Reply from 212.69.36.86: bytes=32 time=51ms TTL=120

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 50ms, Maximum = 54ms, Average = 51ms

C:\Users\Marc>

Microsoft Windows [Version 6.0.6001]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Marc>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=50ms TTL=120

Reply from 212.69.36.86: bytes=32 time=54ms TTL=120

Reply from 212.69.36.86: bytes=32 time=51ms TTL=120

Reply from 212.69.36.86: bytes=32 time=51ms TTL=120

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 50ms, Maximum = 54ms, Average = 51ms

C:\Users\Marc>

 

[deathwish]

issue has passed for me

Pinging oc1.overclock3d.net [212.69.36.85] with 32 bytes of data:

Reply from 212.69.36.85: bytes=32 time=39ms TTL=123

Reply from 212.69.36.85: bytes=32 time=37ms TTL=123

Reply from 212.69.36.85: bytes=32 time=38ms TTL=123

Reply from 212.69.36.85: bytes=32 time=38ms TTL=123

Ping statistics for 212.69.36.85:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 37ms, Maximum = 39ms, Average = 38ms

Pinging oc2.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=38ms TTL=123

Reply from 212.69.36.86: bytes=32 time=44ms TTL=123

Reply from 212.69.36.86: bytes=32 time=39ms TTL=123

Reply from 212.69.36.86: bytes=32 time=38ms TTL=123

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 38ms, Maximum = 44ms, Average = 39ms

 

[mrapoc]

OK I'll drop and reconnect PPoA

My router tends to hang on to a connection for it's dear life so perhaps my line could do with re-training anyway

Got it down to 16ms to idnet

EDIT: Except that one hop was 59ms

I dont think that will incur a retrain mate - it will only retrain your line if you reconnect in the early hours (usually increasing your profile higher, but likely to drop back later on in the day) or if your line is considerably unstable or doing several drops/reconnects in a small amount of time (which it interprets as unstable)

C:\Users\Sam>ping oc1.overclock3d.net

Pinging oc1.overclock3d.net [212.69.36.85] with 32 bytes of data:

Reply from 212.69.36.85: bytes=32 time=50ms TTL=123

Reply from 212.69.36.85: bytes=32 time=48ms TTL=123

Reply from 212.69.36.85: bytes=32 time=51ms TTL=123

Reply from 212.69.36.85: bytes=32 time=47ms TTL=123

Ping statistics for 212.69.36.85:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 47ms, Maximum = 51ms, Average = 49ms

C:\Users\Sam>ping oc2.overclock3d.net

Pinging oc2.overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=50ms TTL=123

Reply from 212.69.36.86: bytes=32 time=50ms TTL=123

Reply from 212.69.36.86: bytes=32 time=48ms TTL=123

Reply from 212.69.36.86: bytes=32 time=50ms TTL=123

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 48ms, Maximum = 50ms, Average = 49ms

Im hoping to see my pings down to the usual 30ms mark in the next 24 hours as interleaving is dropped

 

[nathan]

mine are pretty rubbish although im going through a powerline adapter to my poorly netgear router. With Be, there usually pretty good.

Pinging overclock3d.net [212.69.36.86] with 32 bytes of data:

Reply from 212.69.36.86: bytes=32 time=48ms TTL=121

Reply from 212.69.36.86: bytes=32 time=57ms TTL=121

Reply from 212.69.36.86: bytes=32 time=30ms TTL=121

Reply from 212.69.36.86: bytes=32 time=46ms TTL=121

Ping statistics for 212.69.36.86:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 30ms, Maximum = 57ms, Average = 45ms

 

[FarFarAway]

OK even after rebooting of the router, it still drops down.

Look at this

Pinging www.l.google.com [66.102.9.147] with 32 bytes of data:

Reply from 66.102.9.147: bytes=32 time=1657ms TTL=247

Reply from 66.102.9.147: bytes=32 time=1649ms TTL=247

Reply from 66.102.9.147: bytes=32 time=1171ms TTL=247

Reply from 66.102.9.147: bytes=32 time=890ms TTL=247

Ping statistics for 66.102.9.147:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 890ms, Maximum = 1657ms, Average = 1341ms

 

[mrapoc]

Hey kempez

Could you first contact idnet support and if you so wish, post a reply on the ping thread on idnetters here

altho quite a few people are getting high ones again