Skip to content

Outage tracker / Duolingo

Is Duolingo down?

I'm having a problem

Vendor reports no incidentWhat Duolingo reports

Duolingo reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:31 UTC.

Duolingo's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Duolingo pass from all 10 regions we check.

As of Nov 5, 2026, 3:40 PM UTC, RealUptime's checks of Duolingo passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:40 PM UTC
US-East856 msChecks passing
US-West765 msChecks passing
Europe726 msChecks passing
Asia-Pacific2296 msChecks passing
US-Central1207 msChecks passing
Canada629 msChecks passing
UK730 msChecks passing
Southeast Asia1758 msChecks passing
Australia2851 msChecks passing
South America1528 msChecks passing
their status pagetheir claim, not our reading

Duolingo reports: All systems operational (“All Systems Operational”)

from Duolingo's own status page, checked Nov 5, 2026, 3:13 PM UTC
Duolingo's own status page shows no incident, and our checks of Duolingo pass right now.

Duolingo's own component breakdown, as they publish it

  • DuolingoOperational
  • Duolingo English TestOperational
  • Duolingo for SchoolsOperational

These are Duolingo's components, named and scored by Duolingo. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Duolingo's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Duolingo response time, by region

US-East
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 318ms2026-10-08 UTC: p95 390ms2026-10-09 UTC: p95 335ms2026-10-10 UTC: p95 455ms2026-10-11 UTC: p95 357ms2026-10-12 UTC: p95 308ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 353ms2026-10-15 UTC: p95 398ms2026-10-16 UTC: p95 417ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 244ms2026-10-23 UTC: p95 235ms2026-10-24 UTC: p95 231ms2026-10-25 UTC: p95 177ms2026-10-26 UTC: p95 268ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
2.1sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 504ms2026-10-08 UTC: p95 471ms2026-10-09 UTC: p95 416ms2026-10-10 UTC: p95 495ms2026-10-11 UTC: p95 530ms2026-10-12 UTC: p95 446ms2026-10-13 UTC: p95 536ms2026-10-14 UTC: p95 562ms2026-10-15 UTC: p95 517ms2026-10-16 UTC: p95 588ms2026-10-17 UTC: p95 516ms2026-10-18 UTC: p95 460ms2026-10-19 UTC: p95 519ms2026-10-20 UTC: p95 561ms2026-10-21 UTC: p95 689ms2026-10-22 UTC: p95 532ms2026-10-23 UTC: p95 400ms2026-10-24 UTC: p95 512ms2026-10-25 UTC: p95 489ms2026-10-26 UTC: p95 548ms2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 645ms2026-10-30 UTC: p95 922ms2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 622ms2026-10-08 UTC: p95 466ms2026-10-09 UTC: p95 447ms2026-10-10 UTC: p95 440ms2026-10-11 UTC: p95 490ms2026-10-12 UTC: p95 435ms2026-10-13 UTC: p95 487ms2026-10-14 UTC: p95 675ms2026-10-15 UTC: p95 672ms2026-10-16 UTC: p95 494ms2026-10-17 UTC: p95 414ms2026-10-18 UTC: p95 358ms2026-10-19 UTC: p95 425ms2026-10-20 UTC: p95 402ms2026-10-21 UTC: p95 519ms2026-10-22 UTC: p95 426ms2026-10-23 UTC: p95 475ms2026-10-24 UTC: p95 493ms2026-10-25 UTC: p95 507ms2026-10-26 UTC: p95 532ms2026-10-27 UTC: p95 626ms2026-10-28 UTC: p95 597ms2026-10-29 UTC: p95 589ms2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 945ms2026-11-01 UTC: p95 959ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 2.9s2026-10-23 UTC: p95 2.8s2026-10-24 UTC: p95 2.9s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 8.0s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 983ms2026-11-01 UTC: p95 829ms2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.9s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
US-Central
1.8sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 545ms2026-10-08 UTC: p95 427ms2026-10-09 UTC: p95 426ms2026-10-10 UTC: p95 600ms2026-10-11 UTC: p95 486ms2026-10-12 UTC: p95 680ms2026-10-13 UTC: p95 612ms2026-10-14 UTC: p95 694ms2026-10-15 UTC: p95 709ms2026-10-16 UTC: p95 573ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 427ms2026-10-23 UTC: p95 413ms2026-10-24 UTC: p95 266ms2026-10-25 UTC: p95 226ms2026-10-26 UTC: p95 209ms2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 350ms2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Canada
1.0sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 606ms2026-10-08 UTC: p95 581ms2026-10-09 UTC: p95 564ms2026-10-10 UTC: p95 736ms2026-10-11 UTC: p95 597ms2026-10-12 UTC: p95 667ms2026-10-13 UTC: p95 553ms2026-10-14 UTC: p95 660ms2026-10-15 UTC: p95 690ms2026-10-16 UTC: p95 727ms2026-10-17 UTC: p95 541ms2026-10-18 UTC: p95 573ms2026-10-19 UTC: p95 583ms2026-10-20 UTC: p95 539ms2026-10-21 UTC: p95 699ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 398ms2026-10-24 UTC: p95 454ms2026-10-25 UTC: p95 366ms2026-10-26 UTC: p95 618ms2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 755ms2026-10-29 UTC: p95 868ms2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
UK
1.1sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 734ms2026-10-08 UTC: p95 816ms2026-10-09 UTC: p95 725ms2026-10-10 UTC: p95 759ms2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 589ms2026-10-14 UTC: p95 722ms2026-10-15 UTC: p95 675ms2026-10-16 UTC: p95 534ms2026-10-17 UTC: p95 603ms2026-10-18 UTC: p95 655ms2026-10-19 UTC: p95 852ms2026-10-20 UTC: p95 875ms2026-10-21 UTC: p95 632ms2026-10-22 UTC: p95 439ms2026-10-23 UTC: p95 390ms2026-10-24 UTC: p95 469ms2026-10-25 UTC: p95 419ms2026-10-26 UTC: p95 391ms2026-10-27 UTC: p95 499ms2026-10-28 UTC: p95 471ms2026-10-29 UTC: p95 635ms2026-10-30 UTC: p95 495ms2026-10-31 UTC: p95 545ms2026-11-01 UTC: p95 435ms2026-11-02 UTC: p95 521ms2026-11-03 UTC: p95 847ms2026-11-04 UTC: p95 921ms2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.9s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.6s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
2.9sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 959ms2026-10-11 UTC: p95 941ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 890ms2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
South America
1.9sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 904ms2026-10-11 UTC: p95 926ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 937ms2026-10-14 UTC: p95 710ms2026-10-15 UTC: p95 703ms2026-10-16 UTC: p95 808ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 874ms2026-10-23 UTC: p95 7.0s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 752ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Duolingo

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.

What we measured, function by function

Duolingo answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Duolingo English TestUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Duolingo for SchoolsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Duolingo reports an incident on its status page, and again when it reports it resolved.

Get an email when Duolingo reports an incident

Email me when Duolingo reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Duolingo's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 856msstatus code: 200checked: Nov 5, 2026, 3:27 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
      Checks passinglatency: 765msstatus code: 200checked: Nov 5, 2026, 3:19 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
      Checks passinglatency: 1207msstatus code: 200checked: Nov 5, 2026, 2:45 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
      Checks passinglatency: 629msstatus code: 200checked: Nov 5, 2026, 2:44 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
    Checks passinglatency: 1528msstatus code: 200checked: Nov 5, 2026, 3:40 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 726msstatus code: 200checked: Nov 5, 2026, 3:30 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
      Checks passinglatency: 730msstatus code: 200checked: Nov 5, 2026, 3:35 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2296msstatus code: 200checked: Nov 5, 2026, 3:08 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
      Checks passinglatency: 1758msstatus code: 200checked: Nov 5, 2026, 3:03 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
      Checks passinglatency: 2851msstatus code: 200checked: Nov 5, 2026, 2:51 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 probe events

Duolingo is experiencing increased errors, 38mdeclared on their status page2026-10-27
Duolingo is experiencing increased errors, 6h 57mdeclared on their status page2026-10-21
Duolingo is experiencing increased errors, 2h 26mdeclared on their status page2026-10-21
Duolingo is experiencing increased errors, 27mdeclared on their status page2026-07-19
Duolingo is experiencing increased errors, 20mdeclared on their status page2026-07-19
Duolingo is experiencing increased errors, 53mdeclared on their status page2026-07-18
Duolingo Android app issues, 32mdeclared on their status page2026-06-09
Issues with Video Call and Roleplay, 1h 33mdeclared on their status page2026-05-27

check 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 check readings and Duolingo's own claim at the time, side by side.

Full check history for Duolingo: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Duolingo uptime by RealUptime's checksLive, from this page's own readings.
[![Duolingo uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Duolingo down?", https://realuptime.io/outages/duolingo. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://www.duolingo.com/api/1/version_info
secondary
https://www.duolingo.com/
secondary
https://www.duolingo.com/log-in
secondary
https://englishtest.duolingo.com/
secondary
https://schools.duolingo.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: www.duolingo.com

RealUptime is not affiliated with Duolingo; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.