User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is NWEA down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → nwea.org—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 40 min ago. Last stored result reached it in 318 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 340 ms | 0 |
| Tue 01 | 0 | 0.0 | 317 ms | 0 |
| Tue 03 | 0 | 0.0 | 616 ms | 0 |
| Tue 05 | 0 | 0.0 | 515 ms | 0 |
| Tue 08 | 0 | 0.0 | 464 ms | 0 |
| Tue 10 | 0 | 0.0 | 264 ms | 0 |
| Tue 12 | 0 | 0.0 | 462 ms | 0 |
| Tue 14 | 0 | 0.0 | 407 ms | 0 |
| Tue 16 | 0 | 0.0 | 271 ms | 0 |
| Tue 19 | 0 | 0.0 | 526 ms | 0 |
| Tue 21 | 0 | 0.0 | 314 ms | 0 |
| Tue 23 | 0 | 0.0 | 519 ms | 0 |
| Wed 01 | 0 | 0.0 | 413 ms | 0 |
| Wed 04 | 0 | 0.0 | 551 ms | 0 |
| Wed 06 | 0 | 0.0 | 463 ms | 0 |
| Wed 08 | 0 | 0.0 | 395 ms | 0 |
| Wed 10 | 0 | 0.0 | 342 ms | 0 |
| Wed 12 | 0 | 0.0 | 426 ms | 0 |
| Wed 13 | 0 | 0.0 | 354 ms | 0 |
| Wed 15 | 0 | 0.0 | 390 ms | 0 |
| Wed 17 | 0 | 0.0 | 388 ms | 0 |
| Wed 19 | 0 | 0.0 | 630 ms | 0 |
| Wed 21 | 0 | 0.0 | 334 ms | 0 |
| Wed 23 | 0 | 0.0 | 408 ms | 0 |
| Thu 01 | 0 | 0.0 | 460 ms | 0 |
| Thu 04 | 0 | 0.0 | 394 ms | 0 |
| Thu 06 | 0 | 0.0 | 423 ms | 0 |
| Thu 08 | 0 | 0.0 | 326 ms | 0 |
| Thu 10 | 0 | 0.0 | 369 ms | 0 |
| Thu 12 | 0 | 0.0 | 315 ms | 0 |
| Thu 14 | 0 | 0.0 | 578 ms | 0 |
| Thu 16 | 0 | 0.0 | 631 ms | 0 |
| Thu 18 | 0 | 0.0 | 534 ms | 0 |
| Thu 20 | 0 | 0.0 | 303 ms | 0 |
| Thu 21 | 0 | 0.0 | 399 ms | 0 |
| Thu 23 | 0 | 0.0 | 373 ms | 0 |
| Fri 01 | 0 | 0.0 | 405 ms | 0 |
| Fri 02 | 0 | 0.0 | 408 ms | 0 |
| Fri 04 | 0 | 0.0 | 510 ms | 0 |
| Fri 06 | 0 | 0.0 | 333 ms | 0 |
| Fri 08 | 0 | 0.0 | 351 ms | 0 |
| Fri 10 | 0 | 0.0 | 297 ms | 0 |
| Fri 12 | 0 | 0.0 | 304 ms | 0 |
| Fri 14 | 0 | 0.0 | 437 ms | 0 |
| Fri 16 | 0 | 0.0 | 578 ms | 0 |
| Fri 18 | 0 | 0.0 | 356 ms | 0 |
| Fri 19 | 0 | 0.0 | 596 ms | 0 |
| Fri 20 | 0 | 0.0 | 318 ms | 0 |
Reliability
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live NWEA badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Scheduled Maintenance for November 13, 2026
MAP Growth, PL Online, MAP Reading Fluency, and NWEA State Assessments won't be available Fri, Nov 13 at 5:00 p.m. PST to Sat, Nov 14 10:00 a.m. PST due to scheduled system maintenance. Because we want you to have access to any reports you may request, we highly suggest running your last report two hours prior to the scheduled system maintenance start time. This will help to ensure that the…
Announced by NWEA · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for NWEA yet. Outages of 10 minutes or more get their own page here.
Having trouble with NWEA?
One report per service every 10 minutes from this network. No account.
Follow NWEA
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.
About NWEA
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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 405 ms average, 297–596 ms range across 14 successful checks.
Questions
Is NWEA down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was NWEA last down?
We have not recorded a public NWEA incident since monitoring began 8 days ago.
What is NWEA's uptime?
From our own checks: 100% over 8 days of checks.
How fast does NWEA respond?
405 ms on average over the last 24 hours (297–596 ms).
Does NWEA have an official status page?
Yes, at https://status.nwea.org.
NWEA not working for me but the status is fine. What now?
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.