NBA help and reporting
Use League Pass/streaming support for the billing provider and device involved.
Live Domain Check
Run a live reachability check for nba.com. Compare the regional responses with the problem you see in NBA.
Find NBA help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
NBA scores, articles and League Pass playback are different service paths.
The checker above requests nba.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual NBA action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Use League Pass/streaming support for the billing provider and device involved.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Use League Pass/streaming support for the billing provider and device involved.
Open NBA help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Game/date, live/replay, device/app, region and playback/entitlement error.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to NBA.
These are troubleshooting comparisons, not claims that NBA is currently experiencing a particular incident.
Compare a score page with the affected live game or replay and record the exact access message.
Use NBA's streaming support for the subscription/product and billing provider involved.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when NBA seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open nba.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader NBA issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting NBA support.
Run the nba.com check and compare its original timestamps and responses with your actual error. NBA scores, articles and League Pass playback are different service paths.
Use the official help/reporting resource linked above. Use League Pass/streaming support for the billing provider and device involved.
Compare a score page with the affected live game or replay and record the exact access message. Use NBA's streaming support for the subscription/product and billing provider involved.
Game/date, live/replay, device/app, region and playback/entitlement error.