Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect resolution in CF internal service for Dubai and Johannesburg (and possibly others) #24

Open
PeaStew opened this issue Apr 20, 2022 · 0 comments

Comments

@PeaStew
Copy link

PeaStew commented Apr 20, 2022

curl https://speed.cloudflare.com/cdn-cgi/trace
fl=136f4
h=speed.cloudflare.com
ip=216.155.55.42
ts=1650455342.373
visit_scheme=https
uag=curl/7.68.0
colo=DUR
http=http/2
loc=AE
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

The location in https://speed.cloudflare.com/locations is correct, but for some reason it returns Durban (DUR) South Africa instead of DXB for Dubai and the subsequent test fails. I find no contact page for the Speedtest page to contact anyone, but maybe you know someone who can fix it.

Similarly for Johannesburg it returns Frankfurt (FRA). Latency is obviously horrible and the tests are worthless. I believe that there is probably an indexing error in the internal speedtest API which is not fixable from your code because it is not resolving a specific endpoint, but only for display purposes.

@PeaStew PeaStew changed the title Incorrect resolution in CF internal service for Dubai and Johannesburg (and possible others) Incorrect resolution in CF internal service for Dubai and Johannesburg (and possibly others) Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant