Skip to main content

Is Coursera Down?

No — Coursera is up

Reachable from all 8 checked regions

Average response time: 642ms

Last checked · checks run every 6 hours

Official status page: https://status.coursera.org

Coursera uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
790ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: 100.00% uptime, 16 checks
Jul 31: 100.00% uptime, 40 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 40 checks
Aug 4: 100.00% uptime, 32 checks
Aug 5: 100.00% uptime, 40 checks
Aug 6: 100.00% uptime, 40 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 31 checks
Aug 16: 100.00% uptime, 39 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Jul 20 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
589ms
DNS 33ms TCP 5ms TLS 8ms TTFB 366ms
iad
374ms
DNS 157ms TCP 2ms TLS 3ms TTFB 362ms
jnb
951ms
DNS 248ms TCP 0ms TLS 2ms TTFB 701ms
lax
427ms
DNS 4ms TCP 1ms TLS 3ms TTFB 419ms
lhr
582ms
DNS 27ms TCP 0ms TLS 3ms TTFB 430ms
nrt
753ms
DNS 245ms TCP 1ms TLS 4ms TTFB 602ms
ord
510ms
DNS 158ms TCP 1ms TLS 3ms TTFB 398ms
sin
1088ms
DNS 150ms TCP 1ms TLS 3ms TTFB 875ms
sjc
457ms
DNS 3ms TCP 2ms TLS 5ms TTFB 393ms

What Coursera does

Coursera hosts online courses, professional certificates and full degrees from universities and companies, studied at the learner's own pace. Video lectures, graded assignments and peer review all run inside the platform, and employers and universities route staff and students to it in cohorts, so an outage tends to interrupt a group working towards a shared deadline rather than one person browsing.

What an outage looks like

Lecture videos buffer without ever starting or fail with a playback error while the page around them loads normally. Quiz and assignment submissions return an error at the point of saving, course pages show an empty curriculum, and progress markers can appear reset. Logins loop back to the sign-in screen. The mobile app usually keeps playing already-downloaded lectures while anything new fails.

What to do about it

Check status.coursera.org, but read it narrowly: it tracks Integrations and the LTI Tool, not the learner-facing site, so a site outage can leave it reporting all systems operational. If a graded submission failed, avoid resubmitting repeatedly, because duplicate attempts can eat a limited allowance. Deadlines are set by the institution or partner running the course, so ask them for an extension.

Is it down for everyone, or just you?

If this page says Coursera is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

K
Khan Academy
Zoom
Zoom
Google Workspace
Google Workspace
Notion
Notion

Coursera outage FAQ

Is Coursera down for everyone or just me?
Load a course page in a private window first, because a stale session is the most common cause of a Coursera page that fails for one person alone. If it fails there too, the platform or the network between you and it is the problem. Coursera's own status page covers only integrations, so a multi-region measurement is a better test of whether the site itself is reachable.
Will I lose my answers if Coursera goes down mid-quiz?
Answers you have not submitted live in the browser and are lost if the page is reloaded, so leave the tab open and wait rather than refreshing. Work that reached Coursera before the failure is saved and reappears when the platform recovers. Where an assessment allows a limited number of attempts, a failed submission can still consume one, so raise it with the course staff rather than retrying.
Does a Coursera outage extend my deadline?
Not automatically. Deadlines belong to the university, company or partner running the course, and Coursera does not move them on their behalf. Note the start and end time of the outage while it is happening, because that is the evidence the course staff will ask for. Personal deadlines on self-paced courses can usually be shifted from the course settings without anyone's involvement.
Does the Coursera app work when the website is down?
Partly. Lectures downloaded for offline viewing keep playing, because they are stored on the device, and that often makes the app look healthy while the site is not. Anything needing the platform still fails: new downloads, quiz submissions, discussion posts and progress syncing. Progress recorded offline uploads once the connection is restored, so watching a downloaded lecture during an outage is not wasted.
Why does Coursera's status page say everything is operational?
Because it monitors a narrow slice of the platform. The page lists Integrations and the LTI Tool, which matter to universities wiring Coursera into their own systems, and not the learner-facing website, video delivery or assignment submission. An outage affecting learners can therefore leave the page green. Treat it as authoritative for integrations and use an external measurement for the site.

How we measure this

  • We request Coursera's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Coursera publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Coursera goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required