Skip to content

Outage tracker / Duolingo

Is Duolingo down?

I'm having a problem

Operationalchecked 5 minutes ago

We reached Duolingo from all 10 regions we check.

As of Oct 5, 2026, 8:59 PM UTC, Duolingo answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured Duolingo (since Aug 8, 2026).

our independent probeslive · checked Oct 5, 2026, 8:59 PM UTC
US-East219 msOperational
US-West251 msOperational
Europe306 msOperational
Asia-Pacific677 msOperational
US-Central119 msOperational
Canada819 msOperational
UK615 msOperational
Southeast Asia834 msOperational
Australia570 msOperational
South America275 msOperational
their status pagetheir claim, not our reading

Duolingo publishes no status feed we can read, so the only independent reading here is ours on the left.

Duolingo response time, by region

US-East
393msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 385ms2026-09-07 UTC: p95 342ms2026-09-08 UTC: p95 332ms2026-09-09 UTC: p95 341ms2026-09-10 UTC: p95 340ms2026-09-11 UTC: p95 333ms2026-09-12 UTC: p95 325ms2026-09-13 UTC: p95 392ms2026-09-14 UTC: p95 336ms2026-09-15 UTC: p95 275ms2026-09-16 UTC: p95 382ms2026-09-17 UTC: p95 419ms2026-09-18 UTC: p95 338ms2026-09-19 UTC: p95 310ms2026-09-20 UTC: p95 402ms2026-09-21 UTC: p95 436ms2026-09-22 UTC: p95 379ms2026-09-23 UTC: p95 398ms2026-09-24 UTC: p95 393ms2026-09-25 UTC: p95 333ms2026-09-26 UTC: p95 408ms2026-09-27 UTC: p95 237ms2026-09-28 UTC: p95 212ms2026-09-29 UTC: p95 257ms2026-09-30 UTC: p95 370ms2026-10-01 UTC: p95 405ms2026-10-02 UTC: p95 383ms2026-10-03 UTC: p95 375ms2026-10-04 UTC: p95 320ms2026-10-05 UTC: p95 393ms
Sep 6Sep 20Oct 5
US-West
474msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 612ms2026-09-07 UTC: p95 565ms2026-09-08 UTC: p95 555ms2026-09-09 UTC: p95 313ms2026-09-10 UTC: p95 294ms2026-09-11 UTC: p95 334ms2026-09-12 UTC: p95 408ms2026-09-13 UTC: p95 528ms2026-09-14 UTC: p95 366ms2026-09-15 UTC: p95 382ms2026-09-16 UTC: p95 603ms2026-09-17 UTC: p95 385ms2026-09-18 UTC: p95 625ms2026-09-19 UTC: p95 656ms2026-09-20 UTC: p95 544ms2026-09-21 UTC: p95 513ms2026-09-22 UTC: p95 468ms2026-09-23 UTC: p95 444ms2026-09-24 UTC: p95 489ms2026-09-25 UTC: p95 587ms2026-09-26 UTC: p95 665ms2026-09-27 UTC: p95 511ms2026-09-28 UTC: p95 480ms2026-09-29 UTC: p95 518ms2026-09-30 UTC: p95 576ms2026-10-01 UTC: p95 388ms2026-10-02 UTC: p95 440ms2026-10-03 UTC: p95 541ms2026-10-04 UTC: p95 446ms2026-10-05 UTC: p95 474ms
Sep 6Sep 20Oct 5
Europe
613msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 434ms2026-09-07 UTC: p95 424ms2026-09-08 UTC: p95 385ms2026-09-09 UTC: p95 477ms2026-09-10 UTC: p95 672ms2026-09-11 UTC: p95 453ms2026-09-12 UTC: p95 535ms2026-09-13 UTC: p95 441ms2026-09-14 UTC: p95 488ms2026-09-15 UTC: p95 422ms2026-09-16 UTC: p95 504ms2026-09-17 UTC: p95 510ms2026-09-18 UTC: p95 495ms2026-09-19 UTC: p95 457ms2026-09-20 UTC: p95 468ms2026-09-21 UTC: p95 446ms2026-09-22 UTC: p95 573ms2026-09-23 UTC: p95 465ms2026-09-24 UTC: p95 521ms2026-09-25 UTC: p95 692ms2026-09-26 UTC: p95 664ms2026-09-27 UTC: p95 511ms2026-09-28 UTC: p95 530ms2026-09-29 UTC: p95 536ms2026-09-30 UTC: p95 480ms2026-10-01 UTC: p95 527ms2026-10-02 UTC: p95 438ms2026-10-03 UTC: p95 639ms2026-10-04 UTC: p95 444ms2026-10-05 UTC: p95 613ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 935ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 985ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 829ms2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 980ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
701msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 476ms2026-09-07 UTC: p95 447ms2026-09-08 UTC: p95 488ms2026-09-09 UTC: p95 754ms2026-09-10 UTC: p95 474ms2026-09-11 UTC: p95 713ms2026-09-12 UTC: p95 465ms2026-09-13 UTC: p95 515ms2026-09-14 UTC: p95 688ms2026-09-15 UTC: p95 629ms2026-09-16 UTC: p95 565ms2026-09-17 UTC: p95 423ms2026-09-18 UTC: p95 335ms2026-09-19 UTC: p95 300ms2026-09-20 UTC: p95 319ms2026-09-21 UTC: p95 309ms2026-09-22 UTC: p95 377ms2026-09-23 UTC: p95 668ms2026-09-24 UTC: p95 541ms2026-09-25 UTC: p95 459ms2026-09-26 UTC: p95 534ms2026-09-27 UTC: p95 546ms2026-09-28 UTC: p95 617ms2026-09-29 UTC: p95 607ms2026-09-30 UTC: p95 533ms2026-10-01 UTC: p95 586ms2026-10-02 UTC: p95 569ms2026-10-03 UTC: p95 672ms2026-10-04 UTC: p95 675ms2026-10-05 UTC: p95 701ms
Sep 6Sep 20Oct 5
Canada
803msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 495ms2026-09-07 UTC: p95 573ms2026-09-08 UTC: p95 727ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 478ms2026-09-11 UTC: p95 413ms2026-09-12 UTC: p95 416ms2026-09-13 UTC: p95 522ms2026-09-14 UTC: p95 458ms2026-09-15 UTC: p95 533ms2026-09-16 UTC: p95 366ms2026-09-17 UTC: p95 236ms2026-09-18 UTC: p95 250ms2026-09-19 UTC: p95 311ms2026-09-20 UTC: p95 245ms2026-09-21 UTC: p95 243ms2026-09-22 UTC: p95 376ms2026-09-23 UTC: p95 298ms2026-09-24 UTC: p95 589ms2026-09-25 UTC: p95 662ms2026-09-26 UTC: p95 755ms2026-09-27 UTC: p95 475ms2026-09-28 UTC: p95 539ms2026-09-29 UTC: p95 736ms2026-09-30 UTC: p95 993ms2026-10-01 UTC: p95 348ms2026-10-02 UTC: p95 585ms2026-10-03 UTC: p95 472ms2026-10-04 UTC: p95 647ms2026-10-05 UTC: p95 803ms
Sep 6Sep 20Oct 5
UK
822msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 527ms2026-09-07 UTC: p95 395ms2026-09-08 UTC: p95 412ms2026-09-09 UTC: p95 347ms2026-09-10 UTC: p95 347ms2026-09-11 UTC: p95 372ms2026-09-12 UTC: p95 326ms2026-09-13 UTC: p95 400ms2026-09-14 UTC: p95 404ms2026-09-15 UTC: p95 342ms2026-09-16 UTC: p95 420ms2026-09-17 UTC: p95 508ms2026-09-18 UTC: p95 481ms2026-09-19 UTC: p95 362ms2026-09-20 UTC: p95 560ms2026-09-21 UTC: p95 655ms2026-09-22 UTC: p95 485ms2026-09-23 UTC: p95 472ms2026-09-24 UTC: p95 620ms2026-09-25 UTC: p95 644ms2026-09-26 UTC: p95 641ms2026-09-27 UTC: p95 536ms2026-09-28 UTC: p95 467ms2026-09-29 UTC: p95 488ms2026-09-30 UTC: p95 537ms2026-10-01 UTC: p95 413ms2026-10-02 UTC: p95 842ms2026-10-03 UTC: p95 785ms2026-10-04 UTC: p95 704ms2026-10-05 UTC: p95 822ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.0s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
1.5sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 2.2s2026-09-18 UTC: p95 2.1s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 2.0s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 2.1s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 2.2s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 2.0s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
South America
932msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 932ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 915ms2026-09-10 UTC: p95 976ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 934ms2026-09-13 UTC: p95 878ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 987ms2026-09-16 UTC: p95 829ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 952ms2026-09-19 UTC: p95 883ms2026-09-20 UTC: p95 903ms2026-09-21 UTC: p95 934ms2026-09-22 UTC: p95 729ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 974ms2026-09-25 UTC: p95 784ms2026-09-26 UTC: p95 957ms2026-09-27 UTC: p95 985ms2026-09-28 UTC: p95 966ms2026-09-29 UTC: p95 978ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 932ms
Sep 6Sep 20Oct 5

Is it Duolingo, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Duolingo -- it cannot diagnose Duolingo's own systems.

Get an email when we see Duolingo go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Duolingo, and again when they can reach it again. That is our own measurement from ten regions, not Duolingo's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 219msstatus code: 200checked: Oct 5, 2026, 8:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Duolingo normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 251msstatus code: 200checked: Oct 5, 2026, 8:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Duolingo normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 119msstatus code: 200checked: Oct 5, 2026, 8:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Duolingo normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 819msstatus code: 200checked: Oct 5, 2026, 8:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Duolingo normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 275msstatus code: 200checked: Oct 5, 2026, 8:25 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Duolingo normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 306msstatus code: 200checked: Oct 5, 2026, 8:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Duolingo normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 615msstatus code: 200checked: Oct 5, 2026, 8:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Duolingo normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 677msstatus code: 200checked: Oct 5, 2026, 8:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Duolingo normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 834msstatus code: 200checked: Oct 5, 2026, 8:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Duolingo normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 570msstatus code: 200checked: Oct 5, 2026, 8:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Duolingo normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Duolingo, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Duolingo on September 15, 2026.

Recent outages

No outages on record yet for Duolingo.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Duolingo since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Duolingo covering any window you pick, with our measurements and Duolingo's own claim at the time, side by side.

Full availability history for Duolingo: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Duolingo uptime measured by RealUptimeLive, from this page's own readings.
[![Duolingo uptime measured by RealUptime](https://realuptime.io/outages/duolingo/badge.svg?days=30)](https://realuptime.io/outages/duolingo)
<a href="https://realuptime.io/outages/duolingo"><img src="https://realuptime.io/outages/duolingo/badge.svg?days=30" alt="Duolingo uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Duolingo's SLA implies, from our measurement

At or above your target

We measured none of downtime for Duolingo over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Duolingo's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://www.duolingo.com/api/1/version_info
secondary
https://www.duolingo.com/
RealUptime is not affiliated with Duolingo; the name identifies what we measured, and nothing here speaks for Duolingo's own team. We send a single web request to Duolingo from 10 regions on our own schedule and time the response. We do not see inside Duolingo's systems, do not use an account or real transaction, and are not the same signal Duolingo's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Duolingo is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.