User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
duolingo.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests duolingo.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 106 ms · 1 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 169 ms | 0 |
| 11:45 | 0 | 0.0 | 277 ms | 0 |
| 12:00 | 0 | 0.0 | 261 ms | 0 |
| 12:15 | 0 | 0.0 | 151 ms | 0 |
| 12:30 | 0 | 0.0 | 271 ms | 0 |
| 12:45 | 0 | 0.0 | 98 ms | 0 |
| 13:00 | 0 | 0.0 | 252 ms | 0 |
| 13:15 | 0 | 0.0 | 218 ms | 0 |
| 13:30 | 0 | 0.0 | 81 ms | 0 |
| 13:45 | 0 | 0.0 | 396 ms | 0 |
| 14:00 | 0 | 0.0 | 311 ms | 0 |
| 14:15 | 0 | 0.0 | 214 ms | 0 |
| 14:30 | 0 | 0.0 | 240 ms | 0 |
| 14:45 | 0 | 0.0 | 294 ms | 0 |
| 15:00 | 0 | 0.0 | 371 ms | 0 |
| 15:15 | 0 | 0.0 | 136 ms | 0 |
| 15:30 | 0 | 0.0 | 165 ms | 0 |
| 15:45 | 0 | 0.0 | 199 ms | 0 |
| 16:00 | 0 | 0.0 | 213 ms | 0 |
| 16:15 | 0 | 0.0 | 100 ms | 0 |
| 16:30 | 0 | 0.0 | 150 ms | 0 |
| 16:45 | 0 | 0.0 | 301 ms | 0 |
| 17:00 | 0 | 0.0 | 224 ms | 0 |
| 17:15 | 0 | 0.0 | 137 ms | 0 |
| 17:30 | 0 | 0.0 | 295 ms | 0 |
| 17:45 | 0 | 0.0 | 230 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.
Embed this status badge · JSON
No outages on record for Duolingo 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 Duolingo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Runs on: AWS
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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.