User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
Estimated fix: Not enough NWEA history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9 h; 83 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 45 min ago. Last stored result reached it in 403 ms.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 06:30 | 0 | 0.0 | 333 ms | 0 |
| 08:30 | 0 | 0.0 | 351 ms | 0 |
| 10:45 | 0 | 0.0 | 297 ms | 0 |
| 12:45 | 0 | 0.0 | 304 ms | 0 |
| 14:45 | 0 | 0.0 | 437 ms | 0 |
| 16:45 | 0 | 0.0 | 578 ms | 0 |
| 18:45 | 0 | 0.0 | 356 ms | 0 |
| 19:15 | 0 | 0.0 | 596 ms | 0 |
| 20:15 | 0 | 0.0 | 318 ms | 0 |
| 21:00 | 0 | 0.0 | 308 ms | 0 |
| 23:00 | 0 | 0.0 | 531 ms | 0 |
| 01:00 | 0 | 0.0 | 425 ms | 0 |
| 03:00 | 0 | 0.0 | 415 ms | 0 |
| 03:30 | 0 | 0.0 | 403 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for NWEA 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 NWEA goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NWEA alerts to Slack, Discord or a webhook — free.
We track NWEA (nwea.org) as part of the Cloud & developer group. Advancing learning outcomes for all kids. We empower educators and learners with evidence-based products and services that unlock opportunity.
NWEA publishes an official status page at status.nwea.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 411 ms average, 297–596 ms range across 15 successful checks.
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
We have not recorded a public NWEA incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
411 ms on average over the last 24 hours (297–596 ms). Latest regional checks: US East 557 ms, US West 435 ms, Europe 979 ms, Asia-Pacific 623 ms.
Yes, at https://status.nwea.org.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report NWEA here at once, the problem is on NWEA's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with NWEA. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.