Speed/Ping issue

I went out for a couple of hours and returned to find that my superb download speeds are no more. For several weeks, I’ve been able to count on in excess of 7 mbps with occasional "lows" of 6 mbps. (I’m on the “old” product.) My range this afternoon is 3-1 mbps. My pings are horrendous at 309 ms and worse. Browsing is “sticky” I’ve just viewed this thread over at Netters:

http://www.idnetters.co.uk/forums/index.php?topic=14...

Things weren’t this bad during the Olympics so I’m not blaming Wimbledon.

My exchange appears green.

Any ideas?

______________________________________
IDNet

Sync: 8128 / 832 kbps
IP Profile 7150 kbps
SNR Margin: 17.0-12.5 dB
Line Attenuation: 20.0 dB
SpeedTouch 585

I am approximately 930 metres from the exchange (straight line distance)

In reply to a post by ARD:

Things weren’t this bad during the Olympics so I’m not blaming Wimbledon.

Andy Murray wasn't in the Olympics, and IDNet isn't the only one with problems:

http://forums.thinkbroadband.com/plusnet/t/3660379-t...

~~~~~~~~~~~~
Bill

bill@thinkbroadband.com

Has IDNet acknowledged a problem due to IPlayer use? Presumably speeds/pings are not universally bad asI haven't noticed queries on the General forum.

If it is down to Mr Murray then roll on Monday.

______________________________________
IDNet

Sync: 8128 / 832 kbps
IP Profile 7150 kbps
SNR Margin: 17.0-12.5 dB
Line Attenuation: 20.0 dB
SpeedTouch 585

I am approximately 930 metres from the exchange (straight line distance)

Edited by ARD (Fri 03-Jul-09 16:13:47)

I haven't fully read the IDNetters forums so can't say, but I've seen mention of the same from other ISPs, AAISP I think was one.

Part of the problem is that with most ISPs you don't notice the difference

Funny thing is, my pings are fine, a bit better than usual if anything:

PING bbc.co.uk (212.58.254.252): 56 data bytes
64 bytes from 212.58.254.252: icmp_seq=0 ttl=248 time=19.170 ms
64 bytes from 212.58.254.252: icmp_seq=1 ttl=248 time=18.681 ms
64 bytes from 212.58.254.252: icmp_seq=2 ttl=248 time=19.380 ms
64 bytes from 212.58.254.252: icmp_seq=3 ttl=248 time=19.874 ms
64 bytes from 212.58.254.252: icmp_seq=4 ttl=248 time=20.596 ms
64 bytes from 212.58.254.252: icmp_seq=5 ttl=248 time=19.782 ms
64 bytes from 212.58.254.252: icmp_seq=6 ttl=248 time=19.221 ms
64 bytes from 212.58.254.252: icmp_seq=7 ttl=248 time=19.282 ms
64 bytes from 212.58.254.252: icmp_seq=8 ttl=248 time=19.816 ms
64 bytes from 212.58.254.252: icmp_seq=9 ttl=248 time=18.989 ms
64 bytes from 212.58.254.252: icmp_seq=10 ttl=248 time=19.905 ms
64 bytes from 212.58.254.252: icmp_seq=11 ttl=248 time=19.119 ms
^C
--- bbc.co.uk ping statistics ---
12 packets transmitted, 12 packets received, 0% packet loss
round-trip min/avg/max/stddev = 18.681/19.485/20.596/0.501 ms

~~~~~~~~~~~~
Bill

bill@thinkbroadband.com

I suppose I have got used to perfection since I joined IDNet but then Home SuperMax is no bargain basement product. My pings:

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

Reply from 212.58.254.252: bytes=32 time=182ms TTL=249
Reply from 212.58.254.252: bytes=32 time=188ms TTL=249
Reply from 212.58.254.252: bytes=32 time=171ms TTL=249
Reply from 212.58.254.252: bytes=32 time=185ms 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 = 171ms, Maximum = 188ms, Average = 181ms

And that's good....

______________________________________
IDNet

Sync: 8128 / 832 kbps
IP Profile 7150 kbps
SNR Margin: 17.0-12.5 dB
Line Attenuation: 20.0 dB
SpeedTouch 585

I am approximately 930 metres from the exchange (straight line distance)

In reply to a post by ARD:

And that's good....

No it's not

It's just occurred to me that PlusNet use Ellacoyas for traffic shaping, so can easily check what the traffic is, I'm not sure if IDNet are geared up to get that information easily.

~~~~~~~~~~~~
Bill

bill@thinkbroadband.com

Seems a fellow Netter is also suffering:

http://www.idnetters.co.uk/forums/index.php?PHPSESSI...

(Spool to the end.)

Over at O2 everything is as normal. Though folks from other ISPs might have different stories:

http://forums.thinkbroadband.com/general/t/3660402-a...

______________________________________
IDNet

Sync: 8128 / 832 kbps
IP Profile 7150 kbps
SNR Margin: 17.0-12.5 dB
Line Attenuation: 20.0 dB
SpeedTouch 585

I am approximately 930 metres from the exchange (straight line distance)

I suppose the proof will be to see what happens when the match finishes... and what happens tomorrow afternoon if Murray wins today!

~~~~~~~~~~~~
Bill

bill@thinkbroadband.com

I wouldn't like to be considered a spoilsport....

______________________________________
IDNet

Sync: 8128 / 832 kbps
IP Profile 7150 kbps
SNR Margin: 17.0-12.5 dB
Line Attenuation: 20.0 dB
SpeedTouch 585

I am approximately 930 metres from the exchange (straight line distance)

I'm seeing a general slow down in the afternoons and i'm back with Zen at present. The only thing that worries me with Idnet and in the main prevents my return (and the only reason I left) is this issue with pings.
I remember when Idnet were excellent for their pings/latency when they even bettered much if not all of their ISP competition. Then their WBC upgrade work was completed (early this year) and for weeks things went pear shaped on the latency front.
Now my pings to dutch gaming servers are always stable with Zen, if not as quite as good latency value wise as Idnet once were.

When I now look at idnetters or this TB subforum, there always seems to be an active thread in regard to pings/latency. To me (and maybe I'm wide of the mark) but it's as though people are still rebooting their routers regularly (especially gamers) and that this post 21cn upgrade problem has never really gone away?

Shame really as, as a gamer I had a first rate connection with Idnet prior to the 21CN upgrade.
The more I read too, it seems that the 21CN upgrade has caused a great deal of headaches.