BT Infinity & FTTx Discussion

Main Bath Exchange

Is there anything known to be up currently?

Building is empty so I don't have a clue if it's just an internet outage or a total power cut (I know that the modem isn't on the UPS) but I just noticed this on my graphs when looking around ThinkBroadband:

1b71fd01895268eccc26554e2f3588a4-31-12-2012.png
 
Westyfield2 said:
Is there anything known to be up currently?

Building is empty so I don't have a clue if it's just an internet outage or a total power cut (I know that the modem isn't on the UPS) but I just noticed this on my graphs when looking around ThinkBroadband:

1b71fd01895268eccc26554e2f3588a4-31-12-2012.png
Click to expand...

Just drove in and checked... someone had been in the building and unplugged the load balancer :rolleyes:.

Now speedtesting at 75Mb down, 9Mb up, with a 5ms ping to speedtest.net in London. IP Profile at 77Mb down and 20Mb up.
 
MilanoChris said:
Sub 20ms is fine. You're probably being routed via Sheffield which seems to be a common thing. I did try and raise this with their executive complaints but didn't get very far with it.



This was from them to me. Seems bonkers to me that data originating in London routes via Sheffield and then back to London.

Other FTTC providers don't suffer from this.
Click to expand...

This has been driving me mad - I'm well down in Somerset almost as far south in this country as you can get and to get out onto the internet my data has to go via Sheffield to London... absolutely bonkers. I've also raised it with ELC twice - after the first time they changed the name of the node from .sheffield. to .sf. and told me it was "fixed" :| second time I got a reply similiar to what you did.

Once out of contract I will probably change to another ISP purely over this - even tho its not a major issue as such its just silly - my ping is still under 20ms to game servers but it should be closer to half that and its quite obvious that hop is fairly busy with traffic. (First world problems and all that but its daft).
 
Yeah I totally get your point. I will also be leaving BT when out of contract due to this routing and also their P2P policy; most games update via P2P nowadays and it's a PITA seeing it get throttled when updating.
 
Locky said:
My ping to multiplay server

Pinging 85.236.100.19 with 32 bytes of data:
Reply from 85.236.100.19: bytes=32 time=13ms TTL=54
Reply from 85.236.100.19: bytes=32 time=14ms TTL=54
Reply from 85.236.100.19: bytes=32 time=13ms TTL=54
Reply from 85.236.100.19: bytes=32 time=14ms TTL=54


Dutch server

Pinging 173.199.109.14 with 32 bytes of data:
Reply from 173.199.109.14: bytes=32 time=23ms TTL=116
Reply from 173.199.109.14: bytes=32 time=23ms TTL=116
Reply from 173.199.109.14: bytes=32 time=23ms TTL=116
Reply from 173.199.109.14: bytes=32 time=23ms TTL=116

German server

Pinging 195.122.135.102 with 32 bytes of data:
Reply from 195.122.135.102: bytes=32 time=25ms TTL=111
Reply from 195.122.135.102: bytes=32 time=24ms TTL=111
Reply from 195.122.135.102: bytes=32 time=25ms TTL=111
Reply from 195.122.135.102: bytes=32 time=25ms TTL=111
Click to expand...


Can someone with sky fttc ping these ips. You must be on fastpath.
 
:| thats got to be localised congestion/fault either at the ISP if its not BT (you mentioned BE earlier?) itself or exchange.
 
Last edited:
I have just had a friend run a few tests who is on the same exchange but a different cab and he is having the same poor service as me.
 
Locky said:
Can someone with sky fttc ping these ips. You must be on fastpath.
Click to expand...

Im not on Sky FTTC, but ADSL24 FTTC, here are my pings if it helps....

Code: 
Pinging 85.236.100.19 with 32 bytes of data:
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56


Pinging 173.199.109.14 with 32 bytes of data:
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117


Pinging 195.122.135.102 with 32 bytes of data:
Reply from 195.122.135.102: bytes=32 time=18ms TTL=117
Reply from 195.122.135.102: bytes=32 time=17ms TTL=117
Reply from 195.122.135.102: bytes=32 time=17ms TTL=117
Reply from 195.122.135.102: bytes=32 time=17ms TTL=117
 
V_R said:
Im not on Sky FTTC, but ADSL24 FTTC, here are my pings if it helps....

Code: 
Pinging 85.236.100.19 with 32 bytes of data:
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56
Reply from 85.236.100.19: bytes=32 time=8ms TTL=56


Pinging 173.199.109.14 with 32 bytes of data:
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117
Reply from 173.199.109.14: bytes=32 time=16ms TTL=117


Pinging 195.122.135.102 with 32 bytes of data:
Reply from 195.122.135.102: bytes=32 time=18ms TTL=117
Reply from 195.122.135.102: bytes=32 time=17ms TTL=117
Reply from 195.122.135.102: bytes=32 time=17ms TTL=117
Reply from 195.122.135.102: bytes=32 time=17ms TTL=117
Click to expand...

Much better than BT's what is you location?
 
On BT Infinity 2 (Northwich, Cheshire)


Pinging 85.236.100.19 with 32 bytes of data:
Reply from 85.236.100.19: bytes=32 time=17ms TTL=54
Reply from 85.236.100.19: bytes=32 time=16ms TTL=54
Reply from 85.236.100.19: bytes=32 time=16ms TTL=54
Reply from 85.236.100.19: bytes=32 time=17ms TTL=54

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

Pinging 173.199.109.14 with 32 bytes of data:
Reply from 173.199.109.14: bytes=32 time=25ms TTL=111
Reply from 173.199.109.14: bytes=32 time=26ms TTL=111
Reply from 173.199.109.14: bytes=32 time=25ms TTL=111
Reply from 173.199.109.14: bytes=32 time=25ms TTL=111

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

Pinging 195.122.135.102 with 32 bytes of data:
Reply from 195.122.135.102: bytes=32 time=28ms TTL=111
Reply from 195.122.135.102: bytes=32 time=28ms TTL=111
Reply from 195.122.135.102: bytes=32 time=28ms TTL=111
Reply from 195.122.135.102: bytes=32 time=28ms TTL=111

Ping statistics for 195.122.135.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 28ms, Average = 28ms
Click to expand...
 
(Bt infinity 2, Kent)

C:\Users\Jon>ping 85.236.100.19

Pinging 85.236.100.19 with 32 bytes of data:
Reply from 85.236.100.19: bytes=32 time=9ms TTL=54
Reply from 85.236.100.19: bytes=32 time=8ms TTL=54
Reply from 85.236.100.19: bytes=32 time=9ms TTL=54
Reply from 85.236.100.19: bytes=32 time=9ms TTL=54

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

C:\Users\Jon>ping 173.199.109.14

Pinging 173.199.109.14 with 32 bytes of data:
Reply from 173.199.109.14: bytes=32 time=17ms TTL=110
Reply from 173.199.109.14: bytes=32 time=17ms TTL=110
Reply from 173.199.109.14: bytes=32 time=16ms TTL=110
Reply from 173.199.109.14: bytes=32 time=16ms TTL=110

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

C:\Users\Jon>ping 195.122.135.102

Pinging 195.122.135.102 with 32 bytes of data:
Reply from 195.122.135.102: bytes=32 time=19ms TTL=110
Reply from 195.122.135.102: bytes=32 time=19ms TTL=110
Reply from 195.122.135.102: bytes=32 time=18ms TTL=110
Reply from 195.122.135.102: bytes=32 time=18ms TTL=110

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


good old bt :)
 
V_R said:
Im not on Sky FTTC, but ADSL24 FTTC, here are my pings if it helps....
Click to expand...

Thats pretty much what I would be getting... and should be getting... if BT were doing their job properly :|

@Locky - looks like localised congestion either the exchange has insufficent backhaul, DSLAM or similiar not upto the job and/or overheating under load.

... this is how good BT are... was driving past an FTTC cab the other day and noticed they'd stuck an "Infinity is now here!" poster on it... covering the vents... theres a reason those suckers have vents... feel sorry for whoever is connected to it.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom