High pings again

[vitriol]

just jumped into this thread (been doing other things lately) and I've been having to reboot my router regularly too.  Pings seem to fluctuate wildly.

Reply from 212.69.36.10: bytes=32 time=70ms TTL=59
Reply from 212.69.36.10: bytes=32 time=49ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms 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 = 39ms, Maximum = 70ms, Average = 53ms


Now If I reboot they'll drop to about 25ms.

After trouble with speeds before my holiday they seem to have picked up of late.  So not complaining about that.


So what's been going on?  Anyone care to fill me in?  I really dont have the time to rad 24 pages of posts.

[Simon]

We think IDNet are still manually balancing the networks, but it should all be sorted within a few weeks, when the new hostlink goes live.

[vitriol]

cheers simon

[cjenkins]

Hi,

I've posted on this issue a couple of times. Since I'm not one who likes to make a fuss and since it used to return to decent levels eventually I've never taken it any further. Lately however, every evening without fail, from about 5pm - midnight my pings go way up. This has been going on for the last several weeks and the camel's back finally broke tonight on a gaming server.

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=172ms TTL=121
Reply from 212.58.224.138: bytes=32 time=133ms TTL=121
Reply from 212.58.224.138: bytes=32 time=146ms TTL=121
Reply from 212.58.224.138: bytes=32 time=172ms TTL=121

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 133ms, Maximum = 172ms, Average = 155ms

These are very typical values. Is there a specific reason for this, I see talk about something they're working on at the moment? I'm on GW5. This is the very reason why I left Virgin and joined IDNet, for the first couple of years everything was great but steadily the service has declined. Tell me if I need to call the helpline in the morning and what tests besides the above I need to present to them. Rebooting my router does nothing.

Thanks in advance.

Colin.

[idnetbarry]

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

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

I dont do online gaming but my two sons do on Xbox Live, my ping to idnet use to be 15/20 ms.

[Simon]

All we can say is that the new hostlink went live this morning, and as soon as it's been tested, IDNet will start moving people across, which should alleviate ping issues for those on the Max (8Mb) service.

[Steve]

Mine were poor this evening but seem to have settled with a reboot

[Lance]

It sounds as if the centrals are out of balance again...

[Rik]

Or it's another congested VP, there's a lot of those atm, as BT concentrate on WBC. FWIW, my WBC pings dropped 5ms yesterday as BT put more capacity on.

[zimmerframe]

Hi,

I've posted on this issue a couple of times. Since I'm not one who likes to make a fuss and since it used to return to decent levels eventually I've never taken it any further. Lately however, every evening without fail, from about 5pm - midnight my pings go way up. This has been going on for the last several weeks and the camel's back finally broke tonight on a gaming server.

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=172ms TTL=121
Reply from 212.58.224.138: bytes=32 time=133ms TTL=121
Reply from 212.58.224.138: bytes=32 time=146ms TTL=121
Reply from 212.58.224.138: bytes=32 time=172ms TTL=121

Ping statistics for 212.58.224.138:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 133ms, Maximum = 172ms, Average = 155ms

These are very typical values. Is there a specific reason for this, I see talk about something they're working on at the moment? I'm on GW5. This is the very reason why I left Virgin and joined IDNet, for the first couple of years everything was great but steadily the service has declined. Tell me if I need to call the helpline in the morning and what tests besides the above I need to present to them. Rebooting my router does nothing.

Thanks in advance.

Colin.

I too have been having problems with high pings on the servers that I play on recently.  Last night was really quite bad so I thought I would post in a request this morning about it.  I am on the 8Mb Max service.

It seems that others are already aware of the problem.

I also left Virgin for the same reasons as Colin above and have had until quite recently excellent service

[Gary]

High pings here this morning 

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

C:\Users\>ping idnet.net

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

[Fox]

Arrgh, you have done it again Gary,


C:\Users\Fox>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=111ms TTL=59
Reply from 212.69.36.10: bytes=32 time=107ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=97ms 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 = 97ms, Maximum = 145ms, Average = 115ms

Every time you get high pings you "infect" my connection too 
But as we all know....its all Riks fault 

As usual, IDNet's broadband status shows as "good service", I hate to think what it takes for it to be anything other than good in their eyes. No wonder IDNet is slipping slowly down the charts at DSL Zone - they charge for a premium service but for months have been unable to deliver what they promise. I will give them a week to sort out the new hostlink but if things dont improve I am going to Fast or Newnet, my money is too hard earned to keep throwing at a company that has been providing a substandard service for several months now.

[cjenkins]

Ok so I guess since nobody actually suggests it that there is little advantage to be gained by calling and reporting directly to IDnet? 

Can anyone tell me then when the new hostlink will be finished testing and they will be moving me across. I am on the max service. Like Fox, I will be giving it that period of time to improve and then going elsewhere if it doesn't happen.

[Rik]

I can't tell you, IDNet may be able to, but it is worth calling support - there's been an issue with a central going out of balance again this week.

[cjenkins]

Ok thanks Rik 

[Simon_idnet]

Both of our Centrals were out of balance for a period of time this morning. Where one half is at capacity and the other half is bobbing around at 50 - 60%. It drives us nuts. We are hoping to be able to start moving traffic off of our Centrals and onto the Host Link from early next week. Then this nonsense will be behind us.

Regards
Simon

[zimmerframe]

Thanks Simon

[Simon]

Good news, Simon. 

[Rik]

Great news Simon. 

[Sebby]

Very good news!

[quandam]

 

[zimmerframe]

Nice and quick tonight :-)

[psp83]

Nice and quick tonight :-)

not for me, 2 reboots in an hour

[sawest]

Well I have been paying an extra £10 per month for low latency and priority at the exchange.

I used to get 31ms pings constant and then sub 30ms following my upgrade to Super Max, well for about a month! then. 61 ms if I'm lucky, and above 200 at others.

I ask myself, why am I paying a premium for a sub-standard service?

Well Idnet?

I used to love this company because it was just friggin awesome, but now it has gone the same way as ADSL24 & Plusnet did, go down the friggin pan.

I dont want to spend my life on a technical support line, I want the service I pay for. Is that so much to ask?

I am now paying in the region of 40% more for a service that is infinately worse!

Last chance Idnet, give me a date that u are upgrading your network or give me my MAC!

Simon West.

[sawest]

Yes yada yada yada.

Is now common place with IDNet, come pay over the odds for a sub standard service!

Now fed up with the drivel, and can't be bothered to phone customer support again.

Truth is, since ADSL2+, us poor ADSL noobs have been shafted!

I will not phone customer support about this, I just want my pings back to sub 30ms,

IDNet, this is your only contact from me before I request my MAC. I pay a premium (Super Max) price and have received a sub standard product!

Your choice. Sort it or lose me!

sawest