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
Checks are succeeding and user reports are near the baseline.
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.
Reachable from all 4 regions we check from.
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.
Reaching it
Last check reached it in 721 ms · 8 min ago.
No status feed
Minnesota Timberwolves does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 16 | 0 | 0.0 | 407 ms | 1 |
| Tue 17 | 0 | 0.0 | 259 ms | 0 |
| Tue 18 | 0 | 0.0 | 484 ms | 0 |
| Tue 19 | 0 | 0.0 | 650 ms | 0 |
| Tue 20 | 0 | 0.0 | 290 ms | 0 |
| Tue 21 | 0 | 0.0 | 827 ms | 0 |
| Tue 22 | 0 | 0.0 | 542 ms | 0 |
| Tue 23 | 0 | 0.0 | 1228 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 Minnesota Timberwolves 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 Minnesota Timberwolves goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Minnesota Timberwolves alerts to Slack, Discord or a webhook — free.
Minnesota Timberwolves is listed in our Sports category and checked at nba.com. Live checks and user reports.
Minnesota Timberwolves 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: 97.83% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 845 ms average, 86–6310 ms range across 46 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Minnesota Timberwolves incident since monitoring began 1 day ago.
From our own checks: 97.83% over 1 day of checks.
845 ms on average over the last 24 hours (86–6310 ms). Latest regional checks: US East 335 ms, US West 675 ms, Europe 106 ms, Asia-Pacific 884 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 Minnesota Timberwolves here at once, the problem is on Minnesota Timberwolves's side.