Fed up with idnet.

GameRuk · Jan 05, 2009, 15:26:36

Since last year around june i have had nothing but problems with ping times and packetloss i got the packetloss fixed and ping times was fine for about 2 months, but since then ping are allways higher than normal and never change i have done test after test send them to idnet so for another 2 month i went on here and sent idnet emails asking what the problem was and to see if they could do anything again it was fixed this time for about 20odd days and again the ping is higher i put up with this, but now since last night there even higher i cant be bothered to go through all this again as idnet are not the quickest to sort things out so what i want to know is my next bill is on the 15th on this month is this for the month thats just past or the this month,when i goto another isp if its after the above date will i get a refund for the for the rest of the month or what or will i have to wait till near the end of this month before i switch>?.

Rik · Jan 05, 2009, 15:33:57

It's for the month in advance, Gamer. You'd have to talk to IDNet about a refund, they're due 30 days notice, so it wouldn't be a huge period of time.

MarkE · Jan 06, 2009, 03:57:08

I don't blame you for leaving,I will be yet another customer who once had faith in Idnet and be leaving myself in the not too distant future if the problems with gaming ping persist.
A while back if you was a gamer and asked me is Idnet good? I would have told you that it was superb,but its been nothing but downhill for a while lately,same friends on the same exchange yet
with a different provider do not get my high pings and the 12am disconnects all the time,which is damn unsatisfactory alone,Idnet have really gone downhill in my opinon big no no if anyone asks
me if they should use them

Simon_idnet · Jan 07, 2009, 17:42:58

Hi Guys

We've not got any network problems causing gamers any trouble. I know some very keen (obsessive even) gaming customers who waste no time at all in letting us know if/when we have problems. I've just asked around a few and they are telling me that their service performance is fine. If you want to contact us on support@idnet.com we can check-out your lines for you.

Regards
Simon

Rik · Jan 07, 2009, 17:43:50

Thanks, Simon.

Sebby · Jan 08, 2009, 01:36:00

Quote from: MarkE on Jan 06, 2009, 03:57:08
12am disconnects all the time,which is damn unsatisfactory alone

I see you've never asked for help regarding this particular issue before. If you had, we'd have told you that disconnects are usually caused by local issues, and we could have helped you attempt to solve it. I suspect that the ping issues are related, and not, in fact, to do with IDNet.

Ann · Jan 08, 2009, 09:04:24

If there's a disconnect every day at midnight on the dot, it seems to be caused by the router. I had that with the netgear and don't with the 2700.

Rik · Jan 08, 2009, 09:05:40

It's certainly likely to be a local issue, router or a switch surge. All we need do now is work out what exactly.

VaderDSL · Jan 09, 2009, 23:44:41

Are you near any businesses? I am sure I've heard of some systems activating at a set time that cause a spike which disconnects people nearby.

MarkE · Jan 10, 2009, 19:21:57

Quote from: VaderDSL on Jan 09, 2009, 23:44:41
Are you near any businesses? I am sure I've heard of some systems activating at a set time that cause a spike which disconnects people nearby.

I am right near Green Park business park which has companys like Cisco Systems and such.Thing is I have never had it this bad before with Idnet and Gaming is being ruined even on uk servers
I have just pinged multiplay.co.uk

Reply from 85.236.96.22: bytes=32 time=53ms TTL=124
Reply from 85.236.96.22: bytes=32 time=52ms TTL=124
Reply from 85.236.96.22: bytes=32 time=55ms TTL=124
Reply from 85.236.96.22: bytes=32 time=53ms TTL=124

That will translate to 70ms on a uk server and god knows what on a german one ,given multiplay are only in southampton these are some pretty appalling ping times.

kinmel · Jan 10, 2009, 19:37:33

Pinged from the Router to multiplay...........

ping successful: icmp_seq=10 time=174 ms
ping successful: icmp_seq=11 time=157 ms
ping successful: icmp_seq=12 time=171 ms
ping successful: icmp_seq=13 time=168 ms
ping successful: icmp_seq=14 time=160 ms
ping successful: icmp_seq=15 time=108 ms
ping successful: icmp_seq=16 time=113 ms
ping successful: icmp_seq=17 time=187 ms
ping successful: icmp_seq=18 time=168 ms
ping successful: icmp_seq=19 time=194 ms
ping successful: icmp_seq=20 time=194 ms
ping successful: icmp_seq=21 time=205 ms
ping successful: icmp_seq=22 time=202 ms
ping successful: icmp_seq=23 time=212 ms
ping successful: icmp_seq=24 time=215 ms
ping successful: icmp_seq=25 time=231 ms
ping successful: icmp_seq=26 time=221 ms
ping successful: icmp_seq=27 time=225 ms
ping successful: icmp_seq=28 time=169 ms
ping successful: icmp_seq=29 time=117 ms

I have interleaving turned on

Ted · Jan 10, 2009, 21:51:58

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

ping successful: icmp_seq=0 time=45 ms
ping successful: icmp_seq=1 time=47 ms
ping successful: icmp_seq=2 time=45 ms
ping successful: icmp_seq=3 time=47 ms
ping successful: icmp_seq=4 time=47 ms
ping successful: icmp_seq=5 time=45 ms
ping successful: icmp_seq=6 time=40 ms
ping successful: icmp_seq=7 time=49 ms
ping successful: icmp_seq=8 time=46 ms
ping successful: icmp_seq=9 time=40 ms
ping successful: icmp_seq=10 time=45 ms
ping successful: icmp_seq=11 time=45 ms
ping successful: icmp_seq=12 time=48 ms
ping successful: icmp_seq=13 time=48 ms
ping successful: icmp_seq=14 time=50 ms
ping successful: icmp_seq=15 time=53 ms
ping successful: icmp_seq=16 time=48 ms
ping successful: icmp_seq=17 time=48 ms
ping successful: icmp_seq=18 time=44 ms
ping successful: icmp_seq=19 time=55 ms
ping successful: icmp_seq=20 time=45 ms
ping successful: icmp_seq=21 time=44 ms
ping successful: icmp_seq=22 time=47 ms
ping successful: icmp_seq=23 time=47 ms
ping successful: icmp_seq=24 time=44 ms
ping successful: icmp_seq=25 time=44 ms
ping successful: icmp_seq=26 time=45 ms
ping successful: icmp_seq=27 time=45 ms
ping successful: icmp_seq=28 time=46 ms
ping successful: icmp_seq=29 time=44 ms

From router, also with interleaving turned on. GW5

g7pkf · Jan 11, 2009, 10:02:58

Copyright (c) 2006 Microsoft Corporation. All rights rese

C:\Users\Dean>ping 85.236.96.22 -t

Pinging 85.236.96.22 with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=16ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=16ms TTL=124
Reply from 85.236.96.22: bytes=32 time=22ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124

Ping statistics for 85.236.96.22:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 22ms, Average = 15ms

interleaving off from my laptop (so over wireless as well) on GW5

Simon · Jan 11, 2009, 11:29:52

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=47ms TTL=124
Reply from 85.236.96.22: bytes=32 time=46ms TTL=124
Reply from 85.236.96.22: bytes=32 time=45ms TTL=124
Reply from 85.236.96.22: bytes=32 time=47ms TTL=124

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 47ms, Average = 46ms

vitriol · Jan 11, 2009, 11:59:15

Here's mine

Pinging 85.236.96.22 with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=25ms TTL=124
Reply from 85.236.96.22: bytes=32 time=28ms TTL=124
Reply from 85.236.96.22: bytes=32 time=26ms TTL=124
Reply from 85.236.96.22: bytes=32 time=22ms TTL=124

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 28ms, Average = 25ms

g7pkf · Jan 11, 2009, 12:43:31

Mines the best so far

and my line is probarly the crappiest.

although interleaving is off i am now stable synced at 3200 (line is capable of 5500 but the trains the trains

Rik · Jan 11, 2009, 12:47:54

You're doing better than me, atm, Dean.

Steve · Jan 11, 2009, 14:55:34

Are we comparing like with like here? We have different amounts of data 32 and 64 . Ping times from router and also from local machine. I know for instance if I ping an address from my router the time is greater than that from a client machine.Is this difference due to the difference in the amounts of data been sent?

Ted · Jan 11, 2009, 17:36:20

From a root terminal on machine.

[ted@localhost ~]$ su
Password:
[root@localhost ted]# ping 85.236.96.22 -c 30
PING 85.236.96.22 (85.236.96.22) 56(84) bytes of data.
64 bytes from 85.236.96.22: icmp_seq=1 ttl=124 time=46.6 ms
64 bytes from 85.236.96.22: icmp_seq=2 ttl=124 time=54.2 ms
64 bytes from 85.236.96.22: icmp_seq=3 ttl=124 time=48.5 ms
64 bytes from 85.236.96.22: icmp_seq=4 ttl=124 time=48.9 ms
64 bytes from 85.236.96.22: icmp_seq=5 ttl=124 time=45.1 ms
64 bytes from 85.236.96.22: icmp_seq=6 ttl=124 time=45.9 ms
64 bytes from 85.236.96.22: icmp_seq=7 ttl=124 time=43.8 ms
64 bytes from 85.236.96.22: icmp_seq=8 ttl=124 time=44.1 ms
64 bytes from 85.236.96.22: icmp_seq=9 ttl=124 time=52.2 ms
64 bytes from 85.236.96.22: icmp_seq=10 ttl=124 time=44.7 ms
64 bytes from 85.236.96.22: icmp_seq=11 ttl=124 time=43.0 ms
64 bytes from 85.236.96.22: icmp_seq=12 ttl=124 time=43.2 ms
64 bytes from 85.236.96.22: icmp_seq=13 ttl=124 time=45.5 ms
64 bytes from 85.236.96.22: icmp_seq=14 ttl=124 time=45.8 ms
64 bytes from 85.236.96.22: icmp_seq=15 ttl=124 time=44.2 ms
64 bytes from 85.236.96.22: icmp_seq=16 ttl=124 time=44.3 ms
64 bytes from 85.236.96.22: icmp_seq=17 ttl=124 time=44.8 ms
64 bytes from 85.236.96.22: icmp_seq=18 ttl=124 time=54.9 ms
64 bytes from 85.236.96.22: icmp_seq=19 ttl=124 time=45.2 ms
64 bytes from 85.236.96.22: icmp_seq=20 ttl=124 time=43.5 ms
64 bytes from 85.236.96.22: icmp_seq=21 ttl=124 time=45.8 ms
64 bytes from 85.236.96.22: icmp_seq=22 ttl=124 time=54.0 ms
64 bytes from 85.236.96.22: icmp_seq=23 ttl=124 time=50.1 ms
64 bytes from 85.236.96.22: icmp_seq=24 ttl=124 time=44.9 ms
64 bytes from 85.236.96.22: icmp_seq=25 ttl=124 time=44.9 ms
64 bytes from 85.236.96.22: icmp_seq=26 ttl=124 time=43.2 ms
64 bytes from 85.236.96.22: icmp_seq=27 ttl=124 time=45.5 ms
64 bytes from 85.236.96.22: icmp_seq=28 ttl=124 time=43.9 ms
64 bytes from 85.236.96.22: icmp_seq=29 ttl=124 time=46.1 ms
64 bytes from 85.236.96.22: icmp_seq=30 ttl=124 time=46.5 ms

--- 85.236.96.22 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29076ms
rtt min/avg/max/mdev = 43.036/46.493/54.900/3.331 ms
[root@localhost ted]#

g7pkf · Jan 12, 2009, 09:23:22

okay from the router, mine still look good

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

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

Steve · Jan 12, 2009, 09:46:56

So do I conclude that when using ping the amount of data and source of test makes little difference?

shazzy · Jan 12, 2009, 17:32:15

I'm a gamer and I've not noticed anything wrong to be truly honest.
I have interleaving turned on.

Code Select


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

C:\Users\Sharon>ping 85.236.96.22

Pinging 85.236.96.22 with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=43ms TTL=124
Reply from 85.236.96.22: bytes=32 time=27ms TTL=124
Reply from 85.236.96.22: bytes=32 time=31ms TTL=124
Reply from 85.236.96.22: bytes=32 time=26ms TTL=124

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

C:\Users\Sharon>

Rik · Jan 12, 2009, 17:37:32

Thanks, Shazzy.

MarkE · Jan 13, 2009, 02:11:59

Quote from: g7pkf on Jan 12, 2009, 09:23:22
okay from the router, mine still look good

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

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

Now that is exactly what I use to get with Idnet,alas no more and peak times sees me up into 90ms,I feel a move coming on and its such a damn shame,as I can never fault my actual download speeds with you

Rik · Jan 13, 2009, 08:36:35

Have you talked to support, Mark?