Connectivity diagnostic

Self-service network test. Click Run and we'll probe every public ParlayAPI endpoint from your browser. If the API is up but you can't reach it, this page tells you whether the issue is on your network (ISP filter, corporate firewall, captive portal, DNS hijack) or on our side. For our side outages, also check /status.

ready

Test results

Test	Status	Latency	Note
Press Run diagnostic above.

Server's view of you

{}

ISP reachability right now

If your ISP is in this list and shows reachable_recent, other customers on your ISP are reaching us right now and the issue is local to your network. If your ISP shows no_recent_requests, the ISP is likely filtering us at the resolver. The known_filter_history field flags ISPs with confirmed open complaints.

{}

If everything fails

If every test on this page failed, your network is filtering ParlayAPI entirely. Common causes:

ISP "Security Shield" / parental-controls filters (Spectrum, AT&T DNS, Cox, etc.). Workaround: change your device's DNS to 1.1.1.1 (Cloudflare) or 9.9.9.9 (Quad9), or route via a VPN like Tailscale or Mullvad.
Corporate firewall / web filter. Workaround: ask your IT team to allowlist parlay-api.com.
Captive portal (hotel WiFi, airport WiFi). Workaround: complete the portal's login flow; usually a browser page prompts.
DNS-over-HTTPS misconfig. Try toggling DoH off on your device, retry.

If the diagnostic shows a mix of pass and fail and our status page looks healthy, file an issue with the JSON output below. The X-Request-ID from any failed test is the single most useful piece of info in support tickets.