Anyone seeing increased latency on Xilo's Be LLU service?

Is anyone seeing increased latency on Xilo's Be LLU service today (exchange: SDCRWLY)? From my monitoring graphs it appeared to start just before 10:00am. I've gone from sub 20ms pings to >60ms and beyond when pinging anything.

Not restarted the equipment as yet but will do later if it continues.

Pinging my WAN IP from my VPS server in Hampshire:

--- 95.172.233.xxx ping statistics ---
500 packets transmitted, 483 received, 3% packet loss, time 499755ms
rtt min/avg/max/mdev = 62.030/67.800/86.718/1.853 ms

Pinging time.xilo.net from my VPS server in Hampshire:

--- time.xilo.net ping statistics ---
500 packets transmitted, 500 received, 0% packet loss, time 499777ms
rtt min/avg/max/mdev = 5.143/5.501/8.458/0.325 ms

Live Thinkbroadband BQM
http://www.thinkbroadband.com/ping/share/2b4e93c3bf1...

Live DSL traffic graph via RRDtool from VPS server
http://ganymede.tokenbay.co.uk/graphs/graph_37.html

Live DSL latency graph via RRDtool from VPS server
http://ganymede.tokenbay.co.uk/graphs/graph_30.html

There was an issue on one of Be/O2W's LACs today which caused this according to an outage report received after the incident.

It affected a small number of users but was country wide and wasn't limited to our customers.

Matt

Thanks Matt. It seems to have cleared by 6pm last night.

Hiya Matt, been trying to play BF3 for the past 30 mins but I get server time-outs or disconnected. Like OP my pings to my gateway have jumped from 25ms to 75-80ms too. I'm seeing much higher pings to a lot of servers. Hope it goes away soon.

Does look like there is something not quite right since around 23:25, but only affecting less than 1% of users on Be exchanges.

Please raise a ticket on your account so we can identify you.

Matt

My ping on Sky broadband has gone up a bit tonight too.

Seems to be lots of repairs going on right now across the country thanks to the floods, maybe that is the cause?

Edited by deleted (Sun 15-Jul-12 01:41:56)

W00t! Seems to be fine now, Matt.

Tracing route to lnsxx.uan.thn.uk.murphx.net [89.145.254.xxx]
over a maximum of 30 hops:

1 3 ms 3 ms 4 ms home.gateway.home.gateway [192.168.1.254]
2 19 ms 19 ms 19 ms lnsxx.uan.thn.uk.murphx.net [89.145.254.xxx]

Edited by Khan (Sun 15-Jul-12 02:43:19)

There were a few issues on Talk Talk's network too but that only seemed to occur for about 30 minutes.

Matt

Yep, a lot better than an hour ago...

Pinging 89.145.254.xxx with 32 bytes of data:
Reply from 89.145.254.xxx: bytes=32 time=19ms TTL=254
Reply from 89.145.254.xxx: bytes=32 time=18ms TTL=254
Reply from 89.145.254.xxx: bytes=32 time=19ms TTL=254
Reply from 89.145.254.xxx: bytes=32 time=18ms TTL=254

Ping statistics for 89.145.254.xxx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms

Edited by Khan (Sun 15-Jul-12 02:43:51)

Seems to be back to normal here too.

I monitor my connection like a hawk, and if I notice any changes to my "normal" stats such as lower speeds, increased latency etc I try and and get to the bottom of it lol.

But yes ping seems to be back to normal now:

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=11ms TTL=247
Reply from 212.58.241.131: bytes=32 time=11ms TTL=247
Reply from 212.58.241.131: bytes=32 time=11ms TTL=247
Reply from 212.58.241.131: bytes=32 time=11ms TTL=247

It was going to 25-100ms earlier.

Edited by deleted (Sun 15-Jul-12 03:59:55)