Ping times Jan 28 onwards

[David]

 

[Rik]

If you can tell me which one you're on, Lance, I'll work out whether I'm the problem.

[cjenkins]

Someone let us know if this is likely to be fixed or not. Cos I'm about ready to move if not. I'm on GW5, is there a particular problem there?

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

Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms 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 = 148ms, Maximum = 171ms, Average = 158ms

[mrapoc]

From my experience resetting the PPP/restarting router or whatever doesnt seem to help that much

may as well sit it through until pings drop temporary/idnet fix it

When i reset my PPP/session, sure, sometimes i get low pings - but these only last for like 20 mins 

I hope we get an update soon, or a fix cause im getting close to giving Zen a try  dont want to do that

[MarkE]

Yep its been a bad day again eh 


Reply from 85.236.96.22: bytes=32 time=138ms TTL=124
Reply from 85.236.96.22: bytes=32 time=130ms TTL=124
Reply from 85.236.96.22: bytes=32 time=146ms TTL=124

[mrapoc]

Cod4 is suffering

As is the server hosted on idnet

I cant hit anything (gotta blame somethin eh)

For those who dont game, i find anything over 40ms horrible to play with as will most gamers

[MarkE]

Oh come on,who changed the status form Sub optimal back to good,please pull the other one,such gross lies 


http://www.idnet.net/support/status.jsp

[MarkE]

For those who dont game, i find anything over 40ms horrible to play with as will most gamers

I just played to clan matches on 150ms mate,about as much fun as trying to run through cement

[Lance]

This is not a problem local to GW5 - I'm on DSL4 and also having problems. My ping graph is showing an average ping of just under 80 based on just over 3 hours.

[hellyl]

Cod4 is suffering

As is the server hosted on idnet

I cant hit anything (gotta blame somethin eh)

For those who dont game, i find anything over 40ms horrible to play with as will most gamers

coooooooo yes, I am not the gamer, but hubby is and if I hear anymore, "what website you on now - dont go on there till half time!"  I totally agree anything over 40 is bad, anything over 100 is terrible, the nagging and moaning I hear from hubby is terrible!  He plays in a clan all very serious and organised, he doesnt play every night of the week, but at the moment hes drops to let others play just because of his pings, hes a very sad cod player at the mo, all together now awwwwwwwwwwwwwwwww!

[Lance]

Here are my latest ping results, much lower than earlier.

C:\Users\Lance>ping idnet.net -n 10

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 42ms, Average = 31ms


If only it was consistently like this.

[vitriol]

C:\Documents and Settings\vitriol>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=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms 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 = 21ms, Maximum = 23ms, Average = 22ms

Much better than Saturday night, trying to play on Xbox Live was a joke, infact it was so bad I turned the Xbox off and talked to the missus!!!!!

[uxbod]

Since 11.30pm it appears to have stabilised :-

[Glenn]

Hmmm strange

Straight from the router

Pinging [212.69.36.10] 30 times with: 64 bytes of data

ping successful: icmp_seq=0 time=32 ms
ping successful: icmp_seq=1 time=26 ms
ping successful: icmp_seq=2 time=24 ms
ping successful: icmp_seq=3 time=25 ms


From Dos

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

C:\Users\Glenn>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=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59
Reply from 212.69.36.10: bytes=32 time=98ms 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 = 98ms, Maximum = 141ms, Average = 118ms


Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  home [192.168.1.254]
  2   161 ms   170 ms   155 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   165 ms   153 ms   159 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    65 ms    64 ms    70 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   114 ms   119 ms   131 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   112 ms   103 ms    96 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

That doesn't make sense, at least to me.

[Ray]

Been excellent here since yesterday afternoon.


[attachment deleted by admin]

[Glenn]

That doesn't make sense, at least to me.

Doesn't to me either

[Rik]

Not too dissimilar here, Ray.

[attachment deleted by admin]

[Rik]

Doesn't to me either

That's a relief. The only thing I can think of is a DNS issue in Windows.

[Ray]

I get 20ms pinging idnet.net from the router and 23ms from Windows.

[Rik]

Fairly comparable, Ray.

Router:

ping successful: icmp_seq=0 time=23 ms
ping successful: icmp_seq=1 time=24 ms
ping successful: icmp_seq=2 time=26 ms
ping successful: icmp_seq=3 time=24 ms
ping successful: icmp_seq=4 time=25 ms
ping successful: icmp_seq=5 time=24 ms
ping successful: icmp_seq=6 time=25 ms
ping successful: icmp_seq=7 time=25 ms
ping successful: icmp_seq=8 time=25 ms
ping successful: icmp_seq=9 time=20 ms
ping successful: icmp_seq=10 time=24 ms
ping successful: icmp_seq=11 time=23 ms
ping successful: icmp_seq=12 time=25 ms
ping successful: icmp_seq=13 time=25 ms
ping successful: icmp_seq=14 time=26 ms
ping successful: icmp_seq=15 time=26 ms
ping successful: icmp_seq=16 time=24 ms
ping successful: icmp_seq=17 time=24 ms
ping successful: icmp_seq=18 time=24 ms
ping successful: icmp_seq=19 time=22 ms
ping successful: icmp_seq=20 time=24 ms
ping successful: icmp_seq=21 time=24 ms
ping successful: icmp_seq=22 time=23 ms
ping successful: icmp_seq=23 time=24 ms
ping successful: icmp_seq=24 time=24 ms
ping successful: icmp_seq=25 time=22 ms
ping successful: icmp_seq=26 time=22 ms
ping successful: icmp_seq=27 time=22 ms
ping successful: icmp_seq=28 time=24 ms
ping successful: icmp_seq=29 time=23 ms

Windows:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

ping www.idnet.net -n 10

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

Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59

[David]

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

C:\Users\David>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms 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 = 31ms, Maximum = 33ms, Average = 31ms

C:\Users\David>

[Rik]

I wonder if you line is interleaved, David?

[David]

Shall I check router Rik ?

[David]

What is interleaving? What are its pros and cons? Can I request it to be switched off?

Interleaving is a feature of Up to 8Mb Broadband technology which uses powerful error-correction algorithms to improve broadband speed and stability on long or noisy phone lines. It is employed on BT broadband lines.

Whilst interleaving increases both the speed and stability of your broadband service, it can also increase the delay (latency) of a broadband connection by up to 40ms. Whilst not noticeable to most users, this can adversely affect some highly delay-sensitive applications such as certain online games.

Though not recommended, if you wish interleaving to be permanently switched off on your line, please contact us, allowing five working days for the change to be enabled. If you subsequently find your line performance has worsened and decide you would like interleaving re-enabled, then please contact us as above.

Im none the wiser ,oh yes I am