Permabanned
- Joined
- 9 Aug 2008
- Posts
- 35,707
Oof
BT Infinity Network Infrastructure - The reason behind BT being the worst UK ISP for gaming
- Thread starter Grewks94
- Start date
Oof
They rent the ‘last mile’ from Openreach. That is from the property to the exchange. Within the exchange Sky have their own DSLAM and cablelink to their own Network. This where most of the routing on Skys network is done.
That's really not how that works.
BT are looking into the issue now:
https://www.ispreview.co.uk/index.p...-multiplayer-lag-spikes-during-streaming.html
https://www.ispreview.co.uk/index.p...-multiplayer-lag-spikes-during-streaming.html
Soldato
My ping in BF5 is around 17ms with BT.
Permabanned
- Joined
- 9 Aug 2008
- Posts
- 35,707
This is good to know that BT have acknowledged there is an issue. It's probably routing of some sort.
Soldato
Issue is only present when you are gaming and another device on the network is streaming.
Soldato
We have BT TV too.
Soldato
I think it depends on what is being watched simultaneously then. BT You view or whatever it is I "think" is a forwarded protocol off their main network? I seem to remember it's not directly streaming unless using inbuilt apps. The issue exists when real streaming is involved from the likes of Netflix, SkyGo, iPlayer, Twitch, YouTube etc.
The BF5 servers are in Germany now, I'm surprised you get 17ms, unless you live in mainland europe. EA/DICE really shafted UK players.
Soldato
Hmm... I got the below:
But I remember the days of playing Aces High with 300ms pings and the joy when it went down to 100 ms. Kids these days...
Tracing route to 134.213.37.197 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Local IP
2 1 ms 1 ms 1 ms Local IP
3 4 ms 4 ms 4 ms My external IP
4 * * * Request timed out.
5 21 ms 24 ms 21 ms 31.55.185.188
6 20 ms 20 ms 20 ms core1-hu0-8-0-5.colindale.ukcore.bt.net [195.99.127.146]
7 35 ms 27 ms 23 ms peer2-et0-0-1.slough.ukcore.bt.net [62.172.103.202]
8 21 ms 20 ms 26 ms 195.66.224.116
9 * * * Request timed out.
10 24 ms 21 ms 21 ms 134.213.131.251
11 24 ms 24 ms 27 ms corec-corea.lon5.rackspace.net [162.13.232.10]
12 22 ms 22 ms 22 ms corea-core6.lon3.rackspace.net [164.177.137.13]
13 22 ms 21 ms 21 ms aggr331b-4-aggr331a-4.lon3.rackspace.net [31.222.133.163]
14 21 ms 21 ms 21 ms 134.213.37.197
1 <1 ms <1 ms <1 ms Local IP
2 1 ms 1 ms 1 ms Local IP
3 4 ms 4 ms 4 ms My external IP
4 * * * Request timed out.
5 21 ms 24 ms 21 ms 31.55.185.188
6 20 ms 20 ms 20 ms core1-hu0-8-0-5.colindale.ukcore.bt.net [195.99.127.146]
7 35 ms 27 ms 23 ms peer2-et0-0-1.slough.ukcore.bt.net [62.172.103.202]
8 21 ms 20 ms 26 ms 195.66.224.116
9 * * * Request timed out.
10 24 ms 21 ms 21 ms 134.213.131.251
11 24 ms 24 ms 27 ms corec-corea.lon5.rackspace.net [162.13.232.10]
12 22 ms 22 ms 22 ms corea-core6.lon3.rackspace.net [164.177.137.13]
13 22 ms 21 ms 21 ms aggr331b-4-aggr331a-4.lon3.rackspace.net [31.222.133.163]
14 21 ms 21 ms 21 ms 134.213.37.197
But I remember the days of playing Aces High with 300ms pings and the joy when it went down to 100 ms. Kids these days...
you mean bt are looking into a different issue, gaming priority when the line is being used for other things, not how many hops there are to a server like this thread topic.
Soldato
FTTP Circuit at work
CableCom clearly aren't doing things incredibly correct
CableCom clearly aren't doing things incredibly correct
The latency/lag issues some people are having whilst gaming are due to an issue with BT's core network. One of those hops on the BT traceroutes could be responsible so they are directly related.
Soldato
Never knew there was an issue as I've barely gamed since it started on BT. Good that it'll probably be fixed before it becomes an issue for me.
As for the traceroute ping, BT has always kind of been crap for that tbh.
As for the traceroute ping, BT has always kind of been crap for that tbh.