Pings-AGAIN!

Mohux_Jnr · Dec 17, 2009, 15:56:49

Is anybody else having ping problems again and is there a known reason for it?.

C:\Users\Jons>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes o
Reply from 212.69.36.10: bytes=32 time=81ms TTL=59
Reply from 212.69.36.10: bytes=32 time=77ms TTL=59
Reply from 212.69.36.10: bytes=32 time=84ms TTL=59
Reply from 212.69.36.10: bytes=32 time=94ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 94ms, Average = 84ms

Rik · Dec 17, 2009, 16:02:15

Fine here, Mo:

ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms 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 = 24ms, Maximum = 28ms, Average = 26ms

Assuming you have no background processes running, eg FTP, P2P, then I'd say you are on a congested VP, there's a lot about atm. How are your speeds?

Mohux_Jnr · Dec 17, 2009, 16:10:57

Rik,
Download speed is top notch as always, the upload seems to be struggling for some reason. The pings are not good.

Rik · Dec 17, 2009, 16:13:55

Check with support, they'll be able to take a look at your line for you, and the exchange (though I'd expect speed to be poor if it was congested).

rgt247 · Dec 17, 2009, 16:24:11

Your not alone ! A mate phoned me with the same problem. We are both on the same exchange...

Here's mine...

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms 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 = 114ms, Maximum = 138ms, Average = 127ms

Also I have a few slow dns look up errors. I am currently using open dns.

Ray · Dec 17, 2009, 16:31:22

Does seem to be a problem in some areas, mine are higher than usual.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=90ms TTL=59
Reply from 212.69.36.10: bytes=32 time=109ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms 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 = 90ms, Maximum = 116ms, Average = 107ms

Glenn · Dec 17, 2009, 16:34:38

This maybe the reason

http://aaisp.blogspot.com/search?updated-min=2009-01-01T00%3A00%3A00Z&updated-max=2010-01-01T00%3A00%3A00Z&max-results=50

QuoteBirmingham/Kingston 20CN RAS latency
The latency issue on Birminham and Kingston 20CN BRASs is quite severe, peaking at over 150ms at some times of the day and affecting all lines on these BRASs. It is causing our customers a lot of inconvenience and has been going on all week.

This is affecting around 18% of our customer base and that is low because we have lots of lines on 21CN now and this is a 20CN specific issue. It is causing poor internet access generally and severe disruption to VoIP. The number of broadband users affected accross all ISPs must be huge.

Even so, BT seem to have been dragging their heels on this issue. The latest (from yesterday) was :-

Operate Technical Services and BT Design teams are and have been discussing a proposed action plan to resolve this issue. The correct resource is in place to effect the agreed actions overnight, and this work will be communicated through the Emergency Planned Work.

However, no emergency PEW was issued and nothing happened.

We are obviously very concerned that such a serious issue has not been resolved more quickly. We are waiting for an update around 2pm today.

We have been very patient in this, and trying to work together with BT as partners, but this has dragged on far too long now. Customers may see fault reports on their affected lines later today if we do not hear something more encouraging from BT this afternoon. Unfortunately, reporting faults, which is clearly the right thing to do when a line has such a clear fault, can often lead to disruptive actions by BT staff (changing margins, sending engineers, and even re-jumpering services) so we have to be cautious in taking this approach.

Please rest assured we are doing everything possible to address this serious issue as quickly as possible.

Update: It seems Faraday is also affected but to a much lesser extent.
Update: BT have said they will be doing changes tonight. We will wait and see.
Update: It seems 21CN L-WAT BRASs also affected...
Update: BT have confirmed they will be doing the PEW between 2-6am. Customers are not expected to see any loss of service.

Ray · Dec 17, 2009, 16:38:42

Thanks, Glenn, that seems fairly certain to be affecting me as I'm on a Birmingham BRAS,

Rik · Dec 17, 2009, 16:41:19

There are definitely no issues within IDNet, atm, Rich.

rgt247 · Dec 17, 2009, 16:42:40

I am on the Birmingham BRAS so the hopefully the problems will get fixed soon.

I have had problems this week. BT better get this fixed soon

Thanks for the link cheers...

rgt247 · Dec 17, 2009, 18:26:50

Taken from AAISP link posted by Glen

"Update: Latest MSO report for this issue states anticipated clear time 13th Jan. This is totally unacceptable. We are escalating."

Rik · Dec 17, 2009, 18:27:32

Openreach are beyond a joke, aren't they, Rich.

rgt247 · Dec 17, 2009, 18:35:00

My contention is a joke a the moment... Slow mud like...

I click on a page and wait ! One minute its fine the next slow. Frustrating is an understatement...

I have found a link to keep up to date with BT's progress or lack of Here

Rik · Dec 17, 2009, 18:45:26

And BT will simply say 'take it up with your ISP'. Who can do nothing.

rgt247 · Dec 17, 2009, 19:39:55

To find out which RAS network your connected to this link will help you.

http://www.kitz.co.uk/adsl/RAS.htm

Rik · Dec 17, 2009, 19:46:14

Of course, all bets are off if you're on WBC.

udnylad · Dec 17, 2009, 20:52:06

It is great here when you are getting total packet loss when attempting to ping idenet

Router reboot sorts it for a while. I am up in snowy Aberdeenshire. My Line Stats are normal, it just seems that there is some major congestion somewhere!!!

This is a good ping!!!

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=1807ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1806ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1785ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1786ms 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 = 1785ms, Maximum = 1807ms, Average = 1796ms

Glenn · Dec 17, 2009, 21:13:05

Most likely through Birmingham

Steve · Dec 17, 2009, 21:57:25

My connection has been terrible since midday pings to idnet have increased from 12ms to 30 ms and the internet has been virtually unusable with throughput around 0.5 - 1mbps and now all of a sudden back to what it was this morning. I don't get it. Support suggest it's due to exchange congestion I suspect it goes deeper into the BT network

Sebby · Dec 17, 2009, 22:58:14

No problems here.

Rik · Dec 18, 2009, 08:37:03

I think you're right, Steve, I think BT has oversold their capacity and are juggling bandwidth around, almost (if not actually) in real time, rushing it to where the demand is highest. This long term MUX problem won't be helping, of course.

rgt247 · Dec 18, 2009, 17:24:26

The internet is back to normal for me. As fast as ever. MUCH better then yesterday. But of course there was never a problem. Well according to BT anyway.

A quote from AAISP Status page. Link

"Update: BT have confirmed the work was done last night, although their official status on the incident is that there never was an incident!!!"

Well take it from me there was and is now fixed thankfully........

Glenn · Dec 18, 2009, 17:26:27

Thanks for the update, Rich

Rik · Dec 18, 2009, 17:27:32

BT come from another planet.

Steve · Dec 18, 2009, 17:36:39

I've been here before in the last few days lets hope it stays fixed for a little while.