User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Sports
nba.com · Sports
Something is off: our checks are slower than usual or had a single recent failure.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Slow or flaky
Last check reached it in 2428 ms · 8 min ago.
No status feed
Oklahoma City Thunder does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 16 | 0 | 0.0 | 511 ms | 0 |
| Tue 17 | 0 | 0.0 | 859 ms | 0 |
| Tue 18 | 0 | 0.0 | 484 ms | 0 |
| Tue 19 | 0 | 0.0 | 281 ms | 0 |
| Tue 20 | 0 | 0.0 | 1071 ms | 0 |
| Tue 21 | 0 | 0.0 | 710 ms | 0 |
| Tue 22 | 0 | 0.0 | 1733 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Oklahoma City Thunder yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Oklahoma City Thunder goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Oklahoma City Thunder alerts to Slack, Discord or a webhook — free.
We track Oklahoma City Thunder (nba.com) as part of the Sports group. Live checks and user reports.
Oklahoma City Thunder has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with sports services: ticketing, team app and live-score pages slowing down around game time.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 914 ms average, 143–3121 ms range across 39 successful checks.
Something is off: our checks are slower than usual or had a single recent failure.
We have not recorded a public Oklahoma City Thunder incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
914 ms on average over the last 24 hours (143–3121 ms).
Not one we can read. This page uses independent checks of nba.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For sports services, watch for ticketing, team app and live-score pages slowing down around game time. If many people report Oklahoma City Thunder here at once, the problem is on Oklahoma City Thunder's side.