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.
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 129 ms · 7 min ago.
No status feed
Portland Trail Blazers does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 16 | 0 | 0.0 | 668 ms | 0 |
| Tue 17 | 0 | 0.0 | 643 ms | 0 |
| Tue 18 | 0 | 0.0 | 793 ms | 0 |
| Tue 19 | 0 | 0.0 | 434 ms | 0 |
| Tue 20 | 0 | 0.0 | 809 ms | 0 |
| Tue 21 | 0 | 0.0 | 655 ms | 0 |
| Tue 22 | 0 | 0.0 | 787 ms | 0 |
| Tue 23 | 0 | 0.0 | 396 ms | 0 |
| Wed 00 | 0 | 0.0 | 601 ms | 0 |
| Wed 01 | 0 | 0.0 | 1257 ms | 0 |
| Wed 02 | 0 | 0.0 | 987 ms | 0 |
| Wed 03 | 0 | 0.0 | 665 ms | 0 |
| Wed 04 | 0 | 0.0 | 552 ms | 0 |
| Wed 05 | 0 | 0.0 | 1197 ms | 0 |
| Wed 06 | 0 | 0.0 | 1547 ms | 0 |
| Wed 07 | 0 | 0.0 | 1352 ms | 0 |
| Wed 08 | 0 | 0.0 | 781 ms | 0 |
| Wed 09 | 0 | 0.0 | 519 ms | 0 |
| Wed 10 | 0 | 0.0 | 1223 ms | 0 |
| Wed 11 | 0 | 0.0 | 887 ms | 0 |
| Wed 12 | 0 | 0.0 | 913 ms | 0 |
| Wed 13 | 0 | 0.0 | 697 ms | 0 |
| Wed 14 | 0 | 0.0 | 580 ms | 0 |
| Wed 15 | 0 | 0.0 | 1006 ms | 0 |
| Wed 16 | 0 | 0.0 | 549 ms | 0 |
| Wed 17 | 0 | 0.0 | 494 ms | 0 |
| Wed 18 | 0 | 0.0 | 410 ms | 0 |
| Wed 19 | 0 | 0.0 | 847 ms | 0 |
| Wed 20 | 0 | 0.0 | 349 ms | 0 |
| Wed 21 | 0 | 0.0 | 402 ms | 0 |
| Wed 22 | 0 | 0.0 | 482 ms | 0 |
| Wed 23 | 0 | 0.0 | 655 ms | 0 |
| Thu 00 | 0 | 0.0 | 892 ms | 0 |
| Thu 01 | 0 | 0.0 | 319 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 3 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Portland Trail Blazers 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 Portland Trail Blazers goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Portland Trail Blazers alerts to Slack, Discord or a webhook — free.
We track Portland Trail Blazers (nba.com) as part of the Sports group. Live checks and user reports.
Portland Trail Blazers 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 3 days of checks. No public incidents logged since monitoring began 3 days ago.
Response time over the last 24 hours: 968 ms average, 56–7523 ms range across 172 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Portland Trail Blazers incident since monitoring began 3 days ago.
From our own checks: 100% over 3 days of checks.
968 ms on average over the last 24 hours (56–7523 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 Portland Trail Blazers here at once, the problem is on Portland Trail Blazers's side.