Ping times Jan 28 onwards

[Glenn]

Paul,

I'm still in the 24 - 32ms range

[psp83]

Mine is all over the place

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   129 ms   101 ms   145 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   120 ms   123 ms   126 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   155 ms   160 ms   159 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   137 ms   131 ms   129 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    96 ms   107 ms   101 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   138 ms   226 ms   154 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    63 ms    70 ms    78 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   100 ms   101 ms   100 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   107 ms   100 ms   107 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   123 ms   124 ms   133 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   159 ms   148 ms   148 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   166 ms   150 ms   132 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   152 ms   174 ms   158 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   148 ms   141 ms   152 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   136 ms   134 ms   145 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   131 ms   291 ms   136 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   129 ms   112 ms   116 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   108 ms   136 ms   136 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   104 ms   108 ms   118 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   126 ms   114 ms   120 ms  www.idnet.net [212.69.36.10]

Trace complete.

[zappaDPJ]

Who knows the answer? I know I don't. But a special gamers service seems like a good product idea; a magic bullet. Any takers?

I'd be the first in the queue. I had five glorious years with Pipex when they were still Pipex. During that time my router was rebooted twice, once for a pre-planned infrastructure upgrade which put me out of business for 10 minutes and once to redecorate the living room. My latency to leased UK gaming servers was 35ms rising to 55ms at peak but rarely if ever any more than that.

I can tell you for sure that adding 50ms to a good player's latency will be noticed as far as FPS games are concerned. MMORPGs are a little more tolerant of higher latencies but even so ping anything over 150ms and you will start to have problems.

It's very hard to quantify just how catastrophic it is to people who do not participate in online gaming but in some cases days or even weeks of hard work can be thrown out of the window just because of high latency. World of Warcraft players lagging on a Polarity Shift at Thaddius or a Lava Wall at Sartharion will know exactly what I'm talking about. It doesn't just effect the individual player, it has consequences for the other 24 players involved as far a WoW is concerned.

So the short answer is yes, any ISP offering assurances of low latency for online gaming could make a massive financial killing.

[Glenn]

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

C:\Users\Glenn>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms 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 = 24ms, Maximum = 34ms, Average = 28ms

Have you tried a reboot?

[psp83]

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

C:\Users\Glenn>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms 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 = 24ms, Maximum = 34ms, Average = 28ms

Have you tried a reboot?

Yep, still high.

I did email idnet last night with trace routes and got no reply today.

[psp83]

Getting packet loss now

[cjenkins]

I'm get rightly peeved with this.

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

Reply from 212.69.36.10: bytes=32 time=170ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=133ms 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 = 117ms, Maximum = 170ms, Average = 138ms





This is going on for over a week now. Starting to feel more like an ISP problem than a problem the ISP is having, if you know what I mean. I have turned off my router for long periods of time (like 2 hours) and it has gotten temporarily better but back to this s*** now. Come on Idnet, don't make me want to look for other providers.

[karser]

Problems been on & off for me too today, but one thing that wont help is that theres a new patch just been released for cod:waw today, its 500mb & all the download servers are jammed solid, so there will be a lot of traffic today & probably for most of the weekend, making it harder for idnet to isolate the problem & causing more congestion.

[davej99]

I'd be the first in the queue. ........ I can tell you for sure that adding 50ms to a good player's latency will be noticed ..............  in some cases days or even weeks of hard work can be thrown out of the window just because of high latency. .............  So the short answer is yes, any ISP offering assurances of low latency for online gaming could make a massive financial killing.

Sounds like a separate low latency product might fly. After all these guys need a break.

(I am not a gamer).

[Lance]

I've just done a test of 50 pings to idnet and got the following result (I won't bore with the detail):

Ping statistics for 212.69.36.10:
   Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 41ms, Maximum = 193ms, Average = 123ms

Between 30-40 is typical for my line. Time to run ping graph I think!

[Steve]

Similar here with high ping times >100, reconnected and back to my normal times again.


Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 17ms, Average = 16ms

[Lance]

I've not disconnected but since I've started ping graph I'm back to about 30 with the odd high ping here and there. I'm going to leave it running for a while I think.

[Steve]

What I don't see very well with ping graph is the variation in ping times over a short period of time. If I perform the standard dos ping test x4 recently I often see 2 with normal ping times and the other 2 can be way off. I do not recall seeing this variation before the problems started a week ago.

[Lance]

I think ping graph is good for identifying trends, but as you say, it doesn't necessarily pick up that the reply time changes within a few milli-seconds.

[drummer]

It really has gone a bit bonkers.  I'm not an online gamer so ping speeds aren't that crucial, but I've noticed everything goes a bit sluggish when pings go through the roof.

Are these two screenshots normal?  The first is late evening and the second is early morning.

More confused than anything if truth be told.

[attachment deleted by admin]

[MarkE]

Well the second graph is ideally what most gamers would like to see,I get the same graph more or less from about 12am onward,usually sits at around 11ms then come mid afternoon/evening it bumps up.

the first graph is typically what I and a few others have been getting most evenings where even web browsing is sluggish and online fps gaming is nigh on impossible.

[zappaDPJ]

That's pretty much still the picture from my location, very low latency at off-peak and erratic but generally very high latencies at peak.

[JB]

That's pretty much still the picture from my location, very low latency at off-peak and erratic but generally very high latencies at peak.

Ditto, in Cheshire on GW5.

[cavillas]

Ping. ping ping..........ping ping ping.............piiinnnggg...png..png..ping.

My pings have never been so good.

[Simon_idnet]

Yep, still high.

I did email idnet last night with trace routes and got no reply today.

Hi Paul

I've searched and cannot find an email from you, please could you resend?
Thanks
Simon

[psp83]

Hi Paul

I've searched and cannot find an email from you, please could you resend?
Thanks
Simon

Hi simon, its probly from an address not on your records, it will be from my psp83.com address. I will resend again now thou.

[jameshurrell]

There's obviously something going on and yes I have had downtime in the last few weeks, but I must say that my pings have been very stable throughout.

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

Reply from 212.69.36.10: bytes=32 time=19ms TTL=60
Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=21ms TTL=60
Reply from 212.69.36.10: bytes=32 time=19ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 22ms, Average = 20ms

[Rik]

ATM, my average is 24ms with a range from 21-47.

[psp83]

Hi Paul

I've searched and cannot find an email from you, please could you resend?
Thanks
Simon

I've resent the email now, Just checked my mailbox. Got this message back from my hosts.

This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its recipients after more than 24 hours on the queue on hp13.hostpapa.com.

The message identifier is:     1LVAd5-0003Sw-GO
The subject of the message is: high pings.
The date of the message is:    Thu, 5 Feb 2009 20:15:14 -0000

The address to which the message has not yet been delivered is:

  support@idnet.com
    Delay reason: SMTP error from remote mail server after RCPT TO:<support@idnet.com>:
    host mx2.idnet.net [212.69.40.49]: 450 <*****@psp83.com>:
    Sender address rejected: Greylisted for 5 minutes

No action is required on your part. Delivery attempts will continue for some time, and this warning may be repeated at intervals if the message remains undelivered. Eventually the mail delivery software will give up, and when that happens, the message will be returned to you.



So just incase it happens again, i will also forward you the email from my work email address.

[Rik]

Try support@idnet.net if you still have problems, Paul.