BetQL status: API, auth, latency & outage reports
DownForAI is checking BetQL right now. We monitor 1 surface for availability, latency, and community outage reports.
DownForAI monitors BetQL via a single endpoint — BetQL Web. Current status: unknown — insufficient recent probe data to confirm availability.
No incidents have been logged for BetQL, and no community reports were received in the last 24 hours. Probes run continuously across the configured surfaces.
Current Status
Having issues?
Help other users by reporting if BetQL is not working for you.
Uptime — last 24h
—Network latency — last 20 probes
Incident history (30d)
Reported symptoms
No user reports for BetQL in the last 24 hours.
How we monitor
DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.
Community Discussion
Still having issues with BetQL?
Let the community know and help others experiencing the same problem.