All systems operational
Live uptime, latency and incident history for every Orbistats API product and region — updated in real time and checked every 30 seconds from multiple regions.
99.98%
Rolling 90-day availability across all endpoints.
<50ms
Sub-50ms response time on live score and odds calls.
0
No active incidents at this time.
3
Distributed across three geographic regions.
What uptime and latency actually measure
Uptime is the percentage of health-check requests each component answers successfully over a rolling window, sampled every 30 seconds from more than one region — a single region's blip doesn't flip a component to down. Latency is the median response time for live traffic, not a synthetic ping, so it reflects what your integration actually experiences. Scheduled maintenance is announced in advance and excluded from both numbers; unannounced incidents never are.
Each product is monitored and reported independently, so an issue with one component never hides the status of another.
| Component | Status | 90-day uptime |
|---|---|---|
| Sports Data API | Operational | 99.99% |
| Live Scores API | Operational | 99.97% |
| Odds API | Operational | 99.96% |
| Historical Data API | Operational | 99.99% |
| Webhooks | Operational | 99.98% |
| WebSocket Streaming | Operational | 99.95% |
| Sandbox | Operational | 99.99% |
| Dashboard & Signup | Operational | 99.99% |
Requests are served from the nearest of three regions automatically — no region selection needed on your end. Median latency below reflects live traffic over the last 24 hours.
| Region | Status | Median latency |
|---|---|---|
| US East | Operational | 32ms |
| EU West | Operational | 28ms |
| AP Southeast | Operational | 41ms |
Every incident affecting a component's availability or latency, with root cause and resolution once confirmed. The full status page keeps a complete log beyond the recent entries shown here.
| Date | Component | Impact | Duration |
|---|---|---|---|
| 2026-08-14 | Odds API | Degraded performance | 18 min |
| 2026-07-29 | WebSocket Streaming | Degraded performance | 9 min |
| 2026-07-02 | Live Scores API | Partial outage — AP Southeast | 26 min |
| 2026-06-11 | Dashboard & Signup | Degraded performance | 12 min |
Scheduled maintenance is announced at least 48 hours in advance on the full status page and excluded from the rolling uptime calculation. No maintenance windows are currently scheduled.
Subscribe on the full status page to get an email or webhook the moment anything changes, or poll the RSS feed if you'd rather build your own alerting.
Status says operational, but I'm seeing errors
The handful of things to check before assuming it's a platform incident.
Check your own response first
A 401 or 429 is a client-side auth or rate-limit issue, not a platform incident — these never show up on the status page. Review error codes before filing a report.
Isolated regional issues can lag the page
If you're seeing 5xx errors at volume with status showing operational, contact support with a request ID — isolated regional issues sometimes lag the public status page by a minute or two.
Degraded performance isn't the same as an outage
Degraded performance usually means elevated latency or a partial regional issue while the component still serves most requests successfully. A full outage is always labeled separately.
Common questions
What people ask when reading this page for the first time.
How is Orbistats API uptime calculated?
Uptime is measured as the percentage of successful health-check requests against each component over a rolling window, checked from multiple regions every 30 seconds. A component counts as down only when checks fail from more than one region simultaneously, to avoid flagging a single network blip as an outage.
Where can I get notified about incidents automatically?
Subscribe on the full status page at status.orbistats.com for email or webhook notifications the moment a component's status changes, or watch the status RSS feed if you prefer to poll it yourself.
Does a "degraded performance" status mean requests are failing?
Not necessarily. Degraded performance usually means elevated latency or a partial regional issue while the component still serves most requests successfully. A full outage is always labeled as such, separately from degraded performance.
Are scheduled maintenance windows counted against uptime?
No. Maintenance windows are announced at least 48 hours in advance on the status page and excluded from the rolling uptime calculation, since customers can plan around a known window in a way they can't for an unannounced incident.
My requests are failing but the status page shows operational — what should I check first?
Check your own error response first — a 401 or 429 is a client-side auth or rate-limit issue, not a platform incident. If you're seeing 5xx errors at volume with status showing operational, contact support with a request ID; isolated regional issues sometimes lag the public status page by a minute or two.
Related pages
Explore more of the developer platform.
Changelog
New endpoints, schema changes and deprecations.
Webhooks
Push updates straight to your endpoint.
API Reference
Every endpoint, sport by sport.
Sandbox
Try every endpoint against live sample data.
SDKs
Official client libraries and code examples.
Quickstart
Make your first request in five minutes.
Start free. Upgrade when you need enterprise SLAs.
Self-serve API keys for developers today — dedicated infrastructure, custom feeds and SLAs for sportsbooks and trading desks when you're ready.