High pings again

[Technical Ben]

Hmmm. My pings seem fine now, but only getting around 1mb throughput at the moment. I was getting upt 7 meg, average about 2 to 4 at the weekend. (but thanks for fixing the pings!)

[Simon]

Can only suggest you guys contact IDNet, but I'll also make them aware in the meantime.

[Rik]

not complaining just wondering why.

Distance has something to do with it, Baz, plus traffic levels on the BT part of the network.

[Gary]

Throughput here is fine, BT speed check gives me 6037 which is pretty good for 9am, it has been better but I'm not complaining, pings have dropped by about 1ms but at least its not the mess it was 

[Simon]

Good post, Dave.  I too have often wondered how a few milliseconds can make such a difference in gaming, to the point that people seem to get quite irate over it.  Not being a gamer, though, I probably don't appreciate the frustrations it appears to cause.

[davej99]

These guys pay top money and the frustration is very, very real. I am suggesting that the focus should be on response time excursions rather than lowest ping possible. That is a less confrontation approach that relates directly to ISP capacity, which IDNET seeks to excel in, and to the real world performance of the complete system; player, PC, ISP, onward link and game site. I have seen no evidence that IDNET is anything less than fully committed to its gamers.

[dujas]

I don't understand why you're trying to sugarcoat the situation. Why people want low latency connections, or whether BT Wholesale should accept the majority of the blame is besides the point. Idnet are a communications company that failed to communicate with its customers, over an issue that dragged on for several months. What is the point of a Network Status web page that permanently sat on green with "Good Service", throughout this troubled period?

[Simon_idnet]

Hi Dave

Online games use UDP packets which is a 'connection-less' tansport. That means that you can't send a UDP packet and demand a response. The nearest (albeit imperfect) tool availble to measure respose is an ICMP Echo-reply packet aka "ping". Thus the measurement, by definition, is round-trip (twice the time of a UDP transport in one direction). Not only that but ICMP is often given low priority and so as a tool it cannot be used as a definitive unit of measurement (in the manner of dropping a ruler for example). However, "high pings" do often correlate to a poor gaming experience.

We have been hugly frustrated waiting for this new 21CN capacity (only delivered 16 months late!). During which time we have been unable to afford to install extra short-term 20CN capacity. It has meant that we've had to freeze any growth of the company and juggle capacity hourly in order to try to effectively use what we had available to us. We were not always sucessful at that for which we apologise and we are very grateful to our loyal customers for sticking with us. We look forward to "business as usual" again now. Phew.

Thank you all.
Simon

[davej99]

...... Idnet are a communications company that failed to communicate with its customers, .....

That is not my peception, in fact the exact opposite. For example the preceding post from Simon and many others like it. Thx Simon.

It seems to me IDNET have told us what their plans were from the beginning, what the problems were, when solutions were expected and why the delays.

I have run, served and been served by high technology companies all my working life, some of the best. Technology is fragile, things go haywire. When they do what counts is getting a fix not putting the boot in. It does not help anyone. We seem to be beating up IDNET for getting tight on capacity for reasons beyond their control. This was unforseen, I never noticed and it is fixed. Yet we know many, many broadband customers are served by ISPs that seem to oversell capacity and do nothing. That I have noticed.

[Glenn]

Thanks for the update Simon

[Simon]

Indeed, thanks for your honesty, Simon.

[Ray]

  Thanks, Simon. 

[Sebby]

Thanks for the update, Simon.

[Fox]

Well I found the cause of my low download speeds, my router died on me.......

So i just bought a Netgear DGN2000, seems to be ok so far and my download is back up to 6-7 meg  
Just flashed the firmware up to 1.1.8 (latest on their site) managed not to brick it so things are going good today

[Sebby]

Great stuff.

[psp83]

So i just bought a Netgear DGN2000.

Mines just came now. Hope it works ok on my line.

[zappaDPJ]

Thanks for the update Simon, hopefully you can get back on track now 

[gwidnet]

Just to add my pings seem very good now as well.
I've had the email to ? upgrade to adsl2+ but now I may have a bit of ping stability at last I don't really see there would be any benefit.

[Rik]

Extra bandwidth allowance and the potential for extra speed?

[psp83]

I've noticed pings have increased tonight. Hope its not a sign of problems and that it clears.

[Steve]

Mine are very similar to what they have been for days,no obvious increase for me tonight.

[Glenn]

Still averaging 22ms to IDNet here

[psp83]

back to normal 14-16ms now, was around 70ms (ish).

[Sebby]

Is anyone else experiencing low throughput and high pings around this time each day?

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

  1    29 ms    99 ms    98 ms  speedtouch.lan [192.168.1.254]
  2   497 ms   489 ms   189 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3   523 ms   546 ms   725 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4  1137 ms   801 ms   210 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5  1905 ms  1862 ms  1790 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6  2498 ms  3290 ms  2532 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

Not here, Seb. Could this be related to the Faraday outage?

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.1.254
  2    23 ms    23 ms    23 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    22 ms    21 ms    25 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    22 ms    21 ms    23 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    24 ms    23 ms    23 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    23 ms    23 ms    25 ms  www.idnet.net [212.69.36.10]

Trace complete.