OGS connection issues for BT users (Was: Is OGS running slow? ... no, it isn't)

I’ve been having connection issues for a while now, seeing that red notification all the time.

Both on my phone (I also changed phones recently, so both devices) and on my laptop, on my data plan in my current city and elsewhere and on WiFi at home.

I’m technically inept so I don’t know what could be at fault, anything else with my connection works fine.

So, a couple things:

  1. when you put wss://ai.online-go.com into websocketking.com and hit connect, it’s your browser that connects to that address not websocketking.com servers. So, it’s the same path, you, BT, cloudflare, OGS servers.

  2. If you leave the connection idle without sending any pings the server will disconnect as it assumes the client has gone away, that’s the 30s thing… if you sit there hitting send though it should keep it open.

$ traceroute online-go.com
traceroute to online-go.com (104.26.0.36), 30 hops max, 60 byte packets
1 _gateway.lxd (100.115.92.193) 18.085 ms 0.439 ms 0.045 ms
2 100.115.92.25 (100.115.92.25) 2.464 ms 2.326 ms 2.288 ms
3 192.168.1.254 (192.168.1.254) 5.966 ms 5.937 ms 5.907 ms
4 * * *
5 * * *
6 62.172.102.70 (62.172.102.70) 19.866 ms 62.172.102.68 (62.172.102.68) 15.179 ms 14.427 ms
7 core3-hu0-14-0-6.faraday.ukcore.bt.net (62.172.103.49) 15.444 ms core3-hu0-16-0-6.faraday.ukcore.bt.net (62.172.103.27) 15.792 ms 27.743 ms
8 transit1-xe-0-0-0.faraday.ukcore.bt.net (194.72.16.173) 27.709 ms 27.676 ms 27.645 ms
9 166-49-209-192.gia.bt.net (166.49.209.192) 27.616 ms 166-49-209-128.gia.bt.net (166.49.209.128) 27.544 ms 166-49-209-192.gia.bt.net (166.49.209.192) 15.851 ms
10 t2c4-et-3-1-2-1.uk-lof.gia.bt.net (166.49.250.33) 16.402 ms * t2c4-et-3-0-2-1.uk-lof.gia.bt.net (166.49.250.53) 16.245 ms
11 * * *
12 104.26.0.36 (104.26.0.36) 17.531 ms 141.101.71.93 (141.101.71.93) 25.099 ms 104.26.0.36 (104.26.0.36) 18.355 ms
$

2 Likes

you are away from your house or otherwise have wifi turned off?

I have not done any tests outside of the house yet.
So far I have experienced this on 4 different devices, 3 wifi (phone, chromebook, ipad).
Ethernet Wired Desktop (running Linux) and firefox.

Tonight I had a go lesson and the only way we could do it was to constantly hit the refresh button to view the latest state of the game.

I am on EE mobile which is basically BT mobile data - so it will probably run into the same problems (assuming this is a BT issue).

I ran the cloudfare speed test. See screenshot.

Interesting that it says online gaming status = Poor. My sons have been playing
online games like CS GO and its has worked fine.

2 Likes

Did it actually run the packet loss? The results talk about that in the bottom right that is cropped.

I think if it can’t run it, then it says “0” in that result that we can see.

It’s saying poor because of the 289ms latency.

That’d be because of that upstream latency. CS GO isn’t going to be going through cloudflare, I bet if you do a test to something like speedtest.net your upstream latency will be good just like @denishowe.

So that’s confirmation that there’s definitely something wrong between BT and Cloudflare, I would call BT up and tell them what you’re seeing and see if they know what’s up and if they have an estimate for a fix, it’s definitely their problem.

1 Like

This guy had the same problem back in 2023: https://community.cloudflare.com/t/protected-web-socket-connection-dies-after-30-secs-cloudflare-ipv6-issue/547127.

He’s right, it’s an IP6 thing. The three IP6 addresses for ai.online-go.com all fail 20s after connecting. The three IP4 addresses are all fine - I could keep sending until I got bored.

Connecting via a VPN (to London, Amsterdam or New York) also solved the problem, presumably because it no longer relied on BT connecting to Cloudflare, or maybe because it was IP4 at the crucial point.

I’ll see if EE (my ISP = BT) can help, though it’s going to be fun trying to get something so technical through the front-line “Try turning it off and on again” guys. :slight_smile:

11 Likes

Thanks - great to have your help!

1 Like

That’s really interesting, and disturbing.

4 Likes

Here’s the other part of the results.

1 Like

Could the techies check this problem description so I know what I saying to BT.

PROBLEM: High Upload Latency 289ms between BT and cloudfare.com.
This has caused issues with playing games on online-go.com for people with
BT broadband for the last 3 weeks.

Previously it had been working fine for the past 12 months.

UPDATE: Just tried to report the issue to BT on 151. Their initial reaction is, everything
else is working fine, you just have a problem with latency on 1 website. I have raised
an escalation case as I dont feel they have investigated it. I have the case number and the manager was meant to phone me back into 15 minutes but never did.

3 Likes

Also could someone who is not on BT or Plusnet Broadband, ideally Virgin Media as
they definitely dont got through Oprenreach FTTC (the backbone of the BT network that is sold on to other ISPs).

Please post a screenshot of the upload latency test with Cloudfare.

Goto

https://speed.cloudflare.com

A couple of other questions:

  1. Is there any workround I could put in place at my end to avoid this. Other than changing ISPs. For example could I change my home network to use IPv4 only ?

  2. What I am not clear about is why 289ms is a problem when board updates etc would work perfectly fine if it took 500ms roundtrip, I dont think anyone would ntoice.

TBH I’m not clear why that latency would be a problem either if it is stable.

The screenshots you shared earlier showed our pings timing out at 4 seconds.

I suspect the 289ms latency is more an indicator that there is a saturated link or a piece of failing hardware that is probably dropping upstream packets and causing errors, the speed of light doesn’t move slower in one direction after all.

As for a workaround, @denishowe reports going through a VPN solved it for him, that’d probably work for you as well, I’m guessing not the cloudflare VPN but probably any other one :slight_smile:

As for evidence to present them, definitely point out that a) when going through a VPN the problem goes away, b) your upload to non cloudflare site is good, and c) your download from cloudflare is fine it’s specificallly the upload and that’s why they aren’t seeing a larger complaint.

If y’all want to do some more testing, here are some other sites that use cloudflare that one might be able to figure out how to test to see if uploads or upstream latency are affected: chatgpt.com, opai.com, shopify.com, deepseek.com, medium.com, gitlab.com - I would expect all of them to be somewhat affected. If one can do a test, like an upload or ping or something, to some of those sites and find that it’s slower when going directly to it vs going through a VPN, that’d be a good pile of evidence to present to BT.

2 Likes

For what it’s worth, connecting via IPv6 works fine and is stable as you’d expect for me. So maybe it has to do with specifically IPv6 routing between BT and Cloudflare?

1 Like

I think I am back in business. I installed The VeePN extension to the chrome browser and it has made it work again with OGS.

1 Like

I couldn’t bear the thought of trying to raise it with EE support but I did post on their community forum.

A hard-coded IP4 address in my hosts file fixes the problem for me (until the address changes).

2 Likes

what is the entry you put in your hosts file.

1 Like