User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
coursera.org · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 355 ms · 3 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 1117 ms | 0 |
| 08:15 | 0 | 0.0 | 444 ms | 0 |
| 08:30 | 0 | 0.0 | 450 ms | 0 |
| 08:45 | 0 | 0.0 | 426 ms | 0 |
| 09:00 | 0 | 0.0 | 423 ms | 0 |
| 09:15 | 0 | 0.0 | 468 ms | 0 |
| 09:30 | 0 | 0.0 | 650 ms | 0 |
| 09:45 | 0 | 0.0 | 384 ms | 0 |
| 10:00 | 0 | 0.0 | 524 ms | 0 |
| 10:15 | 0 | 0.0 | 1164 ms | 0 |
| 10:30 | 0 | 0.0 | 957 ms | 0 |
| 10:45 | 0 | 0.0 | 562 ms | 0 |
| 11:00 | 0 | 0.0 | 588 ms | 0 |
| 11:15 | 0 | 0.0 | 348 ms | 0 |
| 11:30 | 0 | 0.0 | 943 ms | 0 |
| 11:45 | 0 | 0.0 | 368 ms | 0 |
| 12:00 | 0 | 0.0 | 651 ms | 0 |
| 12:15 | 0 | 0.0 | 467 ms | 0 |
| 12:30 | 0 | 0.0 | 1044 ms | 0 |
| 12:45 | 0 | 0.0 | 456 ms | 0 |
| 13:00 | 0 | 0.0 | 460 ms | 0 |
| 13:15 | 0 | 0.0 | 308 ms | 0 |
| 13:30 | 0 | 0.0 | 503 ms | 0 |
| 13:45 | 0 | 0.0 | 428 ms | 0 |
| 14:00 | 0 | 0.0 | 405 ms | 0 |
| 14:15 | 0 | 0.0 | 328 ms | 0 |
| 14:30 | 0 | 0.0 | 632 ms | 0 |
| 14:45 | 0 | 0.0 | 467 ms | 0 |
| 15:00 | 0 | 0.0 | 710 ms | 0 |
| 15:15 | 0 | 0.0 | 538 ms | 0 |
| 15:30 | 0 | 0.0 | 345 ms | 0 |
| 15:45 | 0 | 0.0 | 597 ms | 0 |
| 16:00 | 0 | 0.0 | 427 ms | 0 |
| 16:15 | 0 | 0.0 | 305 ms | 0 |
| 16:30 | 0 | 0.0 | 381 ms | 0 |
| 16:45 | 0 | 0.0 | 407 ms | 0 |
| 17:00 | 0 | 0.0 | 517 ms | 0 |
| 17:15 | 0 | 0.0 | 327 ms | 0 |
| 17:30 | 0 | 0.0 | 337 ms | 0 |
| 17:45 | 0 | 0.0 | 422 ms | 0 |
| 18:00 | 0 | 0.0 | 610 ms | 0 |
| 18:15 | 0 | 0.0 | 432 ms | 0 |
| 18:30 | 0 | 0.0 | 406 ms | 0 |
| 18:45 | 0 | 0.0 | 870 ms | 0 |
| 19:00 | 0 | 0.0 | 435 ms | 0 |
| 19:15 | 0 | 0.0 | 395 ms | 0 |
| 19:30 | 0 | 0.0 | 485 ms | 0 |
| 19:45 | 0 | 0.0 | 355 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 Coursera 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 Coursera goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Coursera alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Coursera is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Coursera's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.