Ping time majorly out

MarkE · Jul 01, 2009, 15:36:56

Hey just wondered if anyone else is suffereing from clunky net browsing again as well as ping times.

i am seeing well over 200ms currently to

multiplay.co.uk

as well as google being off the charts.However sync seems fine.

anyone else? I tried a router reboot and as well as powering it off for an hour,but alas its still the same. I am on gw5.

Colin Burns · Jul 01, 2009, 15:43:07

C:\Documents and Settings\colin>ping multiplay.co.uk

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=85ms TTL=124
Reply from 85.236.96.22: bytes=32 time=104ms TTL=124
Reply from 85.236.96.22: bytes=32 time=121ms TTL=124
Reply from 85.236.96.22: bytes=32 time=116ms 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:

i would say pings are a little wacked have you tried a router restart?
Minimum = 85ms, Maximum = 121ms, Average = 106ms

C:\Documents and Settings\colin>

Mohux_Jnr · Jul 01, 2009, 15:49:49

I have got used to the daily reboots at 3.30pm EVERY day to bring my ping back down to normal but today has reached an all time low and has been on going since the upgrade months ago, I am afraid it may well be the final straw for me.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=123ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=100ms 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 = 100ms, Maximum = 138ms, Average = 118ms

MarkE · Jul 01, 2009, 15:53:34

Quote from: Colin Burns on Jul 01, 2009, 15:43:07

i would say pings are a little wacked have you tried a router restart?

C:\Documents and Settings\colin>

Yes i tried a restart as well as powering the router off for well over an hour Colin

dujas · Jul 01, 2009, 16:05:58

I'm on gw5 and have the same problem, router reboot makes no difference. Average ping to www.idnet.net is 147ms, pinging every 15 seconds for half an hour. I've emailed idnet, download speeds don't appear to be affected.

Gary · Jul 01, 2009, 16:07:03

Pings very high here s well

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=200ms TTL=59
Reply from 212.69.36.10: bytes=32 time=215ms TTL=59
Reply from 212.69.36.10: bytes=32 time=208ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms 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 = 163ms, Maximum = 215ms, Average = 196ms

C:\Users\>

Sebby · Jul 01, 2009, 16:10:48

I think this is one that only IDNet can look into.

Gary · Jul 01, 2009, 16:14:14

Just spoke to idnet, they wanted me to drop my firewall to ping me, not something I particularly wanted to do really but its been reported.

Sebby · Jul 01, 2009, 16:15:55

Lucky that's all they wanted you to drop!

Gary · Jul 01, 2009, 16:16:58

Quote from: Sebby on Jul 01, 2009, 16:15:55
Lucky that's all they wanted you to drop!

in this heat Sebby I wouldn't care

zappaDPJ · Jul 01, 2009, 16:17:49

I'm on gw6 with no ping issues.

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

C:\Users\zappaDPJ>ping idnet.com

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

C:\Users\zappaDPJ>
C:\Users\zappaDPJ>ping multiplay.co.uk

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=23ms 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 = 23ms, Maximum = 24ms, Average = 23ms

C:\Users\zappaDPJ>

netgem21 · Jul 01, 2009, 16:19:44

Yep, high pings and slow speeds here too on .dsl4

Ping has started ...

PING www.idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=156.042 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=232.798 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=255.875 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=177.391 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=170.535 ms

--- www.idnet.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 156.042/198.528/255.875/38.726 ms

Steve · Jul 01, 2009, 16:20:34

No good on .net either >100 I blame the tennis, similar issue to what we had with the Olympics? Hopefully improve when Murray finishes

Gary · Jul 01, 2009, 16:21:08

Quote from: zappaDPJ on Jul 01, 2009, 16:17:49
I'm on gw6 with no ping issues.

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

C:\Users\zappaDPJ>ping idnet.com

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

C:\Users\zappaDPJ>
C:\Users\zappaDPJ>ping multiplay.co.uk

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=23ms 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 = 23ms, Maximum = 24ms, Average = 23ms

C:\Users\zappaDPJ>

Are you on ADSL: 2+ though? that would make a difference

Gary · Jul 01, 2009, 16:21:56

Quote from: stevethegas on Jul 01, 2009, 16:20:34
No good on .net either >100 I blame the tennis, similar issue to what we had with the Olympics? Hopefully improve when Murray finishes

I knew there was a reason I did not like Tennis

zappaDPJ · Jul 01, 2009, 16:23:41

Quote from: Gary on Jul 01, 2009, 16:21:08
Are you on ADSL: 2+ though? that would make a difference

I am Gary.

Gary · Jul 01, 2009, 16:26:21

Quote from: zappaDPJ on Jul 01, 2009, 16:23:41
I am Gary.

That makes a difference, last time ping issues happened the few on ADSL2+ did not have the problem.

Colin Burns · Jul 01, 2009, 16:29:54

Quote from: Sebby on Jul 01, 2009, 16:10:48
I think this is one that only IDNet can look into.

they wernt so helpful when i rang and just said that all was well but i think not.

Anaxion · Jul 01, 2009, 16:34:20

on GW5

Pinging www.bbc.net.uk [212.58.251.195] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.58.251.195:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging www.l.google.com [209.85.227.99] with 32 bytes of data:

Reply from 209.85.227.99: bytes=32 time=141ms TTL=247
Reply from 209.85.227.99: bytes=32 time=181ms TTL=247
Reply from 209.85.227.99: bytes=32 time=166ms TTL=247
Reply from 209.85.227.99: bytes=32 time=179ms TTL=247

Ping statistics for 209.85.227.99:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 141ms, Maximum = 181ms, Average = 166ms

any comments?
Thanks

Gary · Jul 01, 2009, 16:36:13

Quote from: Colin Burns on Jul 01, 2009, 16:29:54
they wernt so helpful when i rang and just said that all was well but i think not.

I know, not to impressed with the response I got I have to say.

Steve · Jul 01, 2009, 16:37:36

Probably watching the tennis, I've emailed them with stats and directed them here.

Gary · Jul 01, 2009, 16:40:56

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

C:\Users\>tracert idnet.net

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

1 1 ms <1 ms <1 ms 192.168.0.1
2 179 ms 179 ms 186 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 210 ms 204 ms 215 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 167 ms 159 ms 164 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 166 ms 177 ms 183 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 171 ms 177 ms 187 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\>

Colin Burns · Jul 01, 2009, 16:47:14

Quote from: Gary on Jul 01, 2009, 16:36:13
I know, not to impressed with the response I got I have to say.

i think the tech i got might have worked for Tiscali or Talk Talk and left it off his CV

and still has a copy of the how to lie to customers manual

zappaDPJ · Jul 01, 2009, 16:48:04

Quote from: Gary on Jul 01, 2009, 16:26:21
That makes a difference, last time ping issues happened the few on ADSL2+ did not have the problem.

So those of you that are having problems are on the 8 Mb service? It's something I need to to consider as I'm currently looking at switching back $:-\$

Danni · Jul 01, 2009, 16:49:41

Yup- no ADSL2+ from BT here yet

Adding my pings here to keep that part in one thread

danni@Matilda:~$ ping idnet.net -c5
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=161 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=183 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=194 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=164 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=174 ms

--- idnet.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 161.148/175.722/194.745/12.471 ms