It isn't a real response time.

I remember it now from my O2 days. I think it was always 99ms at all 3 entry positions.

In reply to a post by Pipexer:

In reply to a post by IanBB:

All my O2 routers have displayed this apparent anamoly.

Good grief, well all I can say is, that must be a right piece of [censored] router to do that. Who the hell thinks a response time of 73ms is acceptable in the design of a piece of network equipment? I'd never let [censored] out to customers that did things like that.

It doesn't affect overall pings though, it seems to be a quirk of Thomson based routers.

C:\Users\Ian>ping bbc.co.uk

Pinging bbc.co.uk [212.58.246.104] with 32 bytes of data:
Reply from 212.58.246.104: bytes=32 time=16ms TTL=57
Reply from 212.58.246.104: bytes=32 time=15ms TTL=57
Reply from 212.58.246.104: bytes=32 time=16ms TTL=57
Reply from 212.58.246.104: bytes=32 time=36ms TTL=57

Ping statistics for 212.58.246.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 36ms, Average = 20ms

C:\Users\Ian>

In reply to a post by RobertoS:

It isn't a real response time.

I remember it now from my O2 days. I think it was always 99ms at all 3 entry positions.

Err, well, yes I know that (though I think you will find it is a real response time, Windows hasn't made it up, I think you mean to say it isn't introducing that delay into everything else), but it is simply not acceptable design. How the hell can you expect to monitor for anomalies? What if there was a genuine latency problem between your PC and the first hop? How would you know when it does things like that?

Most BT home hubs are carp, I remember spending ages faffing about one for a neighbour - it would simply NOT port forward as it was told to do.

Basically the delay seems to be in the very first hop from my home hub to 217.47.106.122 which is always the first address after my hub, which apparently is something called a RAS. I wonder if this is the box that BT believe has a fault when my fault status diagram says BT Retail server, or could there be an issue anywhere along the path from my exchange....

Interesting, but I guess I am really just going to have to sit back and see what BT comes up with..

Its almost behaving like I'm on a laggy satellite broadband link!!

217.47.30.0 - 217.47.153.255
netname: BT-MIDBAND
descr: RAS Boxes

traceroute to 217.47.106.122 (217.47.106.122), 64 hops max, 72 byte packets
1 bthomehub (192.168.1.254) 16.876 ms 99.299 ms 100.318 ms
2 217.47.106.122 (217.47.106.122) 1006.069 ms 921.224 ms 1238.396 ms

My annoyance with routers aside, seems like this is "normal" for the homehub for the first hop. It is possible your connection is being saturated. Let's do some more diagnostic.

First of all rebooting the router isn't going to do any harm, so do that anyway if you haven't already.

Get a continual ping running to say thinkbroadband.com

ping thinkbroadband.com -t

While the ping is running try disconnecting all devices from the network apart from your 1 computer, see if things improve.

If not, try testing from another computer and switching the original computer off.

Do a thinkbroadband speedtest and post the results on here

http://www.thinkbroadband.com/speedtest.html

Also make sure nobody is using your wireless, for example.

It could be that there is a problem in your area with the exchange or backhaul etc but usually BT would have picked that up and got it fixed by now, it is not like you are getting packet loss either.

Are you geared up to respond to pings? Perhaps create a tbb ping monitoring account and see what the graph looks overnight.

Edited by Pipexer (Sat 12-Jul-14 21:26:18)

Glad I'm not the only one with issues. Mine has been shocking all day.

Yes, I've done more or less most of that or similar even before I reported it to BT. Routers been rebooted a few times, everything on the network off including vision box, and tests from different computers both wi-fi and wired.

I'm thinking whatever the issue is its further back in the BT network than my house and the line from my house to the exchange, which always seems pretty solid despite my 50db attenuation!

(Theres a link to a speediest in my original post)

I'm on an FTTC line, and it's taking an eternity to view web pages. Am on Runcorn Main exchange. So seems to be happening all over.

Wouldn't mind, apparently the profiles up at the exchange got messed up the other day (or so BT told me) and now this...... Next October can't come soon enough!!

Edited by DarkKobra1977 (Sat 12-Jul-14 23:09:50)

Same here. The issues seem to be at Bt Retail servers and they are not acknowledging the issues. The Hell Desk is sticking to scripts and not offering any explanations of why trace routes to sites show that the greatest latency is in the BTR infrastructure nodes. So unless some one suggests a new route, in my opinion we can only sit tight.

almost 3am and the performance is far better, but still high maxes...

It must be loading/traffic related, I suspect tomorrow afternoon and evening it will be back to treacle...

64 bytes from 212.58.244.66: icmp_seq=95 ttl=50 time=52.435 ms
64 bytes from 212.58.244.66: icmp_seq=96 ttl=50 time=56.722 ms
64 bytes from 212.58.244.66: icmp_seq=97 ttl=50 time=51.492 ms
64 bytes from 212.58.244.66: icmp_seq=98 ttl=50 time=53.548 ms
64 bytes from 212.58.244.66: icmp_seq=99 ttl=50 time=51.736 ms

--- www.bbc.net.uk ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 50.753/76.907/271.336/43.077 ms