Sudden increase in average latency

Started by JamesAllen, Sep 20, 2012, 15:17:58

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

JamesAllen

As is often the case, I assume this is down to the local exchange but thought I'd throw it out there in case anyone is seeing this.

Basically for the past few hours I've seen average latency on my connection go to hell:



I know it often fluctuates as I am doing a lot of upstream but not to the level you can see on the graph over the past few hours. Average ping seems to be about 250ms whereas it's normally 30ms or so.

Here's a ping to the bbc:

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of da
Reply from 212.58.241.131: bytes=32 time=324ms TTL=247
Reply from 212.58.241.131: bytes=32 time=130ms TTL=247
Reply from 212.58.241.131: bytes=32 time=139ms TTL=247
Reply from 212.58.241.131: bytes=32 time=173ms TTL=247
Reply from 212.58.241.131: bytes=32 time=201ms TTL=247
Reply from 212.58.241.131: bytes=32 time=215ms TTL=247
Reply from 212.58.241.131: bytes=32 time=266ms TTL=247
Reply from 212.58.241.131: bytes=32 time=299ms TTL=247
Reply from 212.58.241.131: bytes=32 time=305ms TTL=247
Reply from 212.58.241.131: bytes=32 time=183ms TTL=247
Reply from 212.58.241.131: bytes=32 time=61ms TTL=247
Reply from 212.58.241.131: bytes=32 time=122ms TTL=247
Reply from 212.58.241.131: bytes=32 time=113ms TTL=247
Reply from 212.58.241.131: bytes=32 time=136ms TTL=247
Reply from 212.58.241.131: bytes=32 time=226ms TTL=247
Reply from 212.58.241.131: bytes=32 time=280ms TTL=247
Reply from 212.58.241.131: bytes=32 time=198ms TTL=247
Reply from 212.58.241.131: bytes=32 time=275ms TTL=247
Reply from 212.58.241.131: bytes=32 time=315ms TTL=247

..and a trace route:

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

  1    <1 ms    <1 ms    <1 ms  devserver.jwadevelopments.int [192.168.0.150]
  2     2 ms   173 ms   183 ms  telehouse-gw4-lo1.idnet.net [212.69.63.98]
  3   172 ms   269 ms    61 ms  telehouse-gw6-gi4-400.idnet.net [212.69.63.246]

  4   207 ms   103 ms   231 ms  telehouse-gw5-gi4-400.idnet.net [212.69.63.245]

  5   190 ms   103 ms   247 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  6     *        *        *     Request timed out.
  7   101 ms   271 ms    85 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
  8   192 ms   339 ms   264 ms  132.185.255.60
  9   265 ms   210 ms   196 ms  212.58.241.131

Trace complete.

As I said, I expect this is down to local exchange issues but anyone else seeing anything like this currently or have any other ideas?

It's killing radio streaming due to the high latency. I recall this happening not so long ago as well.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

My FTTC line isn't showing problems, nor are any of the admin lines.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JamesAllen

Thanks guys. Most likely the usual local exchange rubbish we get from time to time. Will keep my eye on it. Hopefully it will clear soon.

JamesAllen

Seemed to return to normal around 4pm. :)

andrue

I got a poor 35ms earlier this evening from SpeedTest.net then it went back to 24 which still isn't brilliant. Mind you Tuesday evening it was showing 5ms so on average it's probably about right  :laugh: