Poor pings/ degraded speeds

Neither pings nor download speeds have been up to what IDNet usually deliver for about a fortnight. This morning both seem to have deteriatated. Here�s my pings:

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

Reply from 212.58.224.138: bytes=32 time=177ms TTL=122
Reply from 212.58.224.138: bytes=32 time=161ms TTL=122
Reply from 212.58.224.138: bytes=32 time=177ms TTL=122
Reply from 212.58.224.138: bytes=32 time=181ms TTL=122

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

Pinging barclays.co.uk [213.219.1.141] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.219.1.141:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=176ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms 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 = 139ms, Maximum = 178ms, Average = 160ms

Here�s a tracert:

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 2 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 176 ms 190 ms 185 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 154 ms 152 ms 144 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 172 ms 167 ms 138 ms rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
5 180 ms 183 ms 185 ms 212.58.238.153
6 160 ms 162 ms 174 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.


I can almost always count on download speed of in excess to 7 mbps down to 6.5 mbps. Today, I�m sub-5 mbps for much of the time. Anybody else?


EDIT: I disconnected from IDnet for 10 minutes (not DSL) and find both speeds and pings have improved, though the gateways are the same. However, for the second time in recent weeks, I cannot login to my Barclays account. Tracerts and pings suggest problems somewhere. Is this a Barclays or IDNet issue?

Edited by ARD (Mon 27-Jul-09 11:33:54)

A number of users are reporting ping issues. The only common factor is that they have GW5 logins, though this really shouldn't be a problem these days as connection to the centrals is on a round-robin basis. Most of us are not seeing the problem. I'd suggest contacting support.

As to Barclays, I've just logged in, so maybe it's a site issue.

You logged into Barclays account without a hitch? I'm having a terrible time. I can reach the site but when I click the Big Blue Button to login I don't reach the name/IOD number page.

EDIT: Tried again. There must be site issues:

Barclays secure online banking
Barclays5 - Sorry - Barclays Online Banking is currently unavailable
Select the green 'Next' button to continue to www.barclays.co.uk.

Edited by ARD (Mon 27-Jul-09 12:02:57)

Mea culpa. It was the Barclaycard site I logged into, sorry.

Tried again. There must be site issues:

Barclays secure online banking
Barclays5 - Sorry - Barclays Online Banking is currently unavailable
Select the green 'Next' button to continue to www.barclays.co.uk.



Anyway, speeds/pings are normal again

Edited by ARD (Mon 27-Jul-09 12:05:28)

LloydsTSB is running like a snail on Mogadon this morning, maybe they're trying to tell us something

LOL Barclays is broken:

http://forums.thinkbroadband.com/general/t/3675559-r...

Probably to stop me moving my savings to a higher rate account. I don't think the site could have been overwhelmed by customers impressed by their F/R bond offers. Here's the latest:

http://www.theregister.co.uk/2009/07/27/barclays_ban...

Edited by ARD (Mon 27-Jul-09 15:24:14)

Just posted at IDNetters:

IDNet have become aware of an issue affecting throughput for a handful of Max users.
They are working to resolve the issue, and are manually re-balancing the centrals again.

If you have a problem, please do NOT reboot your router,
but instead run a ping to www.idnet.net and email support with the results for help.

Thanks, Rik

My pings/ speeds have been great-normal since 11.30 am. Here's a sample ping:

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

Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms 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 = 32ms, Maximum = 37ms, Average = 33ms

Barclay's login page contains 96 Errors and 30 warning(s) according to the W3C validator. And the page itself contains this message:

We're currently experiencing technical problems in Online Banking that mean some of you may not be able to log in to the service. We apologise for any inconvenience this may cause and suggest you try logging in again later.

Message updated 27 July 2009.

Seriously, would you really entrust them with your credit card details or online banking?