polar tinsel
I’m seeing a consistent issue where the Cloudflare Turnstile script at:
https://challenges.cloudflare.com/turnstile/v0/api.js
returns HTTP 500 on every request. This happens across multiple networks and devices, so it does not appear to be client-side.
Summary:
• Any request to /turnstile/v0/api.js returns HTTP 500.
• Reproducible on: home ISP, mobile hotspot, VPN (multiple exits), and a second device.
• DNS resolves correctly to Cloudflare IPs (104.18.94.41 / 104.18.95.41 + matching IPv6).
• TLS handshake is valid with a proper certificate from Google Trust Services.
• No proxy, no firewall interception, nothing rewriting HTTPS.
• Happens with HTTP/2 and HTTP/1.1, IPv4 and IPv6, any User-Agent.
Example curl output:
HTTP/2 500
server: cloudflare
cache-control: no-store
cf-ray: 9a07cb32fb735002-MCI
The Ray IDs indicate Cloudflare edge nodes are generating the 500 directly.
Impact:
Websites using Turnstile show “Please unblock challenges.cloudflare.com” because the script never loads.
What I’m trying to confirm:
Is there a known issue or outage with Turnstile’s script-serving backend or a misconfigured edge deployment? The behavior is identical across multiple networks and regions, which makes it unlikely to be a local problem.
I can provide more Ray IDs, timestamps, or logs if needed.
dusky gorge
