Ping time majorly out

Sebby · Jul 04, 2009, 11:02:05

I don't disagree with what's been said. We can only pass on what IDNet tell us. We don't have any secret information. If IDNet say there's no problem within their network, we have to accept that, as there's no way of proving otherwise.

I agree that IDNet have been to blame in the past when BT were originally blamed, and I do see what you mean about BT always getting the blame, Dopamine.

All I can suggest is that if anyone is not happy with the level of service they receive, or do not believe what IDNet are saying, they request their MAC and move to another ISP.

idnetbarry · Jul 04, 2009, 12:27:25

Pinging idnet.net [212.69.36.10] with 32 bytes of d
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59

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

Thats better

Pings should be ok now Andy Murry is out of wimbledon.

Flippin iplayer.

dujas · Jul 04, 2009, 12:58:16

Entanet have been transparent with BT Centrals usage, they used to have real-time graphs of capacity. Although their transition to IPSC (IPStream Connect) wasn't generally well received by most of their customers.

I don't think at any point I blamed BT, I just pointed out the costs may restrict the capacity Idnet is able to afford and be a viable business.

Technical Ben · Jul 04, 2009, 14:37:47

In IDNet's defence, I'd like to give my experience.
I was with O2 on their Home Access service (non LLU). And they just buy the bare minimum off bandwidth of BT. The congestion is unbearable. And customer services has nothing to offer to help except "have you checked your pc/cables". My pings every evening went to 140ms+ and speed was erratic.
Immediatly after the switch to IDNet my ping is now 50ms. The highest it gets during really busy times (like the tennis) is 100ms. I'm perfectly happy with this.
And when I sent a little emial to customer support mentioning my pings, and if there is anything I can do to help, they immediately offered to turn off interleaving.
Now that's miles ahead of the great, but scripted, customer support I got from O2.

So IDNet may not be perfect. But they seem miles ahead in customer service and reliability of connection than the likes of O2.

Really hope your connection gets sorted.

I agree with you on the issue of all ISPs suffering from contention ration problems. I suppose it's the fault of "up to 8meg" when really we might need to go back to the old "pay for 2mb get 2mb, pay for 8mb get 8mb". Having those who really need 8mb and can get it pay a premium and those who can only get 2mb pay for that might help.

glen · Jul 04, 2009, 18:05:22

I was with o2 as well Ben, so I know exactly what you mean,good connection during the day useless after 5 oclock.

Lance · Jul 04, 2009, 23:57:31

I'm going to have to disagree with one of Dopamine's comments. I don't believe that negative comments on this forum about Idnet are met with opposite comments from loyal customers. One thing I've always liked about this forum is that people posting are honest and that means that if Idnet are to blame then people are critical. However, I believe that even though they are critical of Idnet, they appreaciate that things happen that should and are generally happy as long as lessons are learnt and there are no repeats.

Lance · Jul 04, 2009, 23:58:44

Apologies, that should have said things happen that should not

Ninny · Jul 05, 2009, 22:46:14

Well, it's nearly 11pm on a Sunday night and still the ping times are shocking! Doesn't seem the tennis can be blamed at the moment.

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

Reply from 212.69.36.10: bytes=32 time=202ms TTL=59
Reply from 212.69.36.10: bytes=32 time=155ms TTL=59
Reply from 212.69.36.10: bytes=32 time=202ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59

Sebby · Jul 05, 2009, 23:11:48

That really is bad, Ninny. Let IDNet know.

Rik · Jul 06, 2009, 15:16:44

That looks like the results I got from my dongle.

Ninny · Jul 06, 2009, 19:19:57

Whenever I've tried a ping test the results are wholly inconsistant, if I try a ping now for example, here are the results:

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=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=101ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59

This is totally unacceptable for gaming, but even when it was stable I was getting 60-70 in-game, when most people have 30 pings in the UK. The 60 - 70 ping is slightly higher to what I got on BT but some days I would get a 40 - 50 ping which was much better, however it's never been that low with IDnet.

Is anybody else on gw5 still getting this inconsistant ping problem? At the moment it's skyrocketing up to 200 ping all game and is just unplayable and makes it impossible for me to play competitively (ie for money/prizes, which I use to do).

I'm not going to bother complaining to IDnet Sebby, because I'm getting moved to a new BT line on gw7 in a few days, hopefully I'll see an improvement and be able to have interleaving taken off, here's hoping..

Rik · Jul 06, 2009, 19:21:53

No point in me commenting, Ninny as, although I'm on GW5 I'm also on WBC.

dujas · Jul 06, 2009, 21:33:18

27ms ping average on gw5 atm. The latency problem was just a one day affair for me, that being women's semi-finals day with a 200ms+ ping, strangely the day of Murry's game was fine. Rebooting your router or disconnecting/re-connecting PPP might help.

glen · Jul 06, 2009, 21:45:07

Quote from: Ninny on Jul 06, 2009, 19:19:57
Whenever I've tried a ping test the results are wholly inconsistant, if I try a ping now for example, here are the results:

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=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=101ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59

This is totally unacceptable for gaming, but even when it was stable I was getting 60-70 in-game, when most people have 30 pings in the UK. The 60 - 70 ping is slightly higher to what I got on BT but some days I would get a 40 - 50 ping which was much better, however it's never been that low with IDnet.

Is anybody else on gw5 still getting this inconsistant ping problem? At the moment it's skyrocketing up to 200 ping all game and is just unplayable and makes it impossible for me to play competitively (ie for money/prizes, which I use to do).

I'm not going to bother complaining to IDnet Sebby, because I'm getting moved to a new BT line on gw7 in a few days, hopefully I'll see an improvement and be able to have interleaving taken off, here's hoping..

Hi Ninny I'm getting more or less the same problem if it's any consolation, very frustrating indeed, especially when your teenage son is playing games online
then starts cracking up because he keeps getting kicked from the server. It's doing my loaf in!!

cjenkins · Jul 06, 2009, 22:34:17

Hi,

I'm also on gw5. Been having the high latency since Satruday I think.

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

Reply from 212.58.254.252: bytes=32 time=160ms TTL=249
Reply from 212.58.254.252: bytes=32 time=109ms TTL=249
Reply from 212.58.254.252: bytes=32 time=147ms TTL=249
Reply from 212.58.254.252: bytes=32 time=146ms TTL=249

Ping statistics for 212.58.254.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 160ms, Average = 140ms

Simon · Jul 06, 2009, 23:27:26

It can't be down to the tennis now. All I can suggest is to contact IDNet.

mist · Jul 07, 2009, 11:06:57

My pings are also high at 11.00am on GW5

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=180ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms 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 = 180ms, Average = 147ms

Fox · Jul 07, 2009, 12:30:44

I know this may be of no help but I am experiencing the same same problems on GW5 of high ping (ping to idnet is currently 175-180ms, it is normally 40ish). Despite the high ping my throughput is still fine (ran several speed tests all show between 5 and 6 meg, I sync at 8128)

I rang Idnet and explained the situation, they said there was no problem on their network. They also said I should drop them an email about the problem which sounds silly to me as I was on the phone to them about it....not the sort of customer service that I was expecting, just sounds like being fobbed off.

Simon · Jul 07, 2009, 12:39:25

Did they not ask for router stats, and a BT Soeedtest in the email, Fox?

Simon · Jul 07, 2009, 12:41:07

I know it's not much help, but I am also on GW5, and my pings seem normal:

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

Reply from 212.58.254.252: bytes=32 time=32ms TTL=249
Reply from 212.58.254.252: bytes=32 time=33ms TTL=249
Reply from 212.58.254.252: bytes=32 time=31ms TTL=249
Reply from 212.58.254.252: bytes=32 time=32ms TTL=249

Ping statistics for 212.58.254.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 33ms, Average = 32ms

C:\Documents and Settings\Simon>ping idnet.com

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

Reply from 212.69.36.10: bytes=32 time=32ms 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=31ms 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 = 29ms, Maximum = 34ms, Average = 31ms

Fox · Jul 07, 2009, 12:42:11

They didnt ask for anything, just said email them about the problem

Fox · Jul 07, 2009, 12:52:08

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms 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 = 132ms, Maximum = 167ms, Average = 153ms

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=181ms 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 = 181ms, Average = 164ms

I just tried to play on a couple of my normal game servers (I play on american servers a lot as I am in an american clan for gaming) and got kicked for high ping. I hope this issue is resolved soon as I have a match tonight and if my ping stays high like this I will not be able to play

dujas · Jul 07, 2009, 12:52:29

I think the point needs to be emphasised to support that it appears to be a gw5 problem. Any ping tests they do from within their own network are unlikely to uncover the problem.

Simon_idnet · Jul 07, 2009, 14:10:59

Occasionally one of our pipes may attract more traffic than the others and become congested. We have enough aggregated to bandwidth to cope with normal loads (massive iPlayer events notwithstanding) so a simple router reboot should force a reconnection to a different pipe.

Regards
Simon

Mohux_Jnr · Jul 07, 2009, 16:57:29

Simon,
The test results below were taken 5 minutes after our telephone conversation and forced reboot from your end. 16ms as we spoke on the phone but within 5 minutes back to this.
It is what I have been experiencing for weeks, long before the tennis and no amount of rebooting works for more than 20 mins max in my case between the hours of 4-8pm.

Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms 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 = 127ms, Maximum = 157ms, Average = 141ms