Coursera Outage History
Coursera is up right nowPingoru has recorded 50 incidents for Coursera: 0 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 522 (0%) |
Incidents, newest first
Notice October 20, 2025 Coursera site is currently down 7h 3m
Started Oct 20, 2025, 03:38 PM UTC· resolved Oct 20, 2025, 10:42 PM UTC
- investigating Oct 20, 2025, 03:38 PM UTC
Our site is currently down due to a widespread Amazon AWS service outage. We are working to restore access as soon as possible, thank you for your patience.
- identified Oct 20, 2025, 06:47 PM UTC
AWS services are in the process of being restored, and we are working to restore Coursera access as soon as possible.
- monitoring Oct 20, 2025, 09:47 PM UTC
AWS has not yet achieved full recovery, but we are seeing continued stabilization of the Coursera platform as more parts of the platform are regaining functionality. We will continue to monitor and work towards full recovery.
- resolved Oct 20, 2025, 10:42 PM UTC
Coursera platform is back to fully operational, thank you for your patience and understanding.
Notice April 7, 2025 Coursera.org is experiencing interruptions 19m
Started Apr 07, 2025, 09:40 PM UTC· resolved Apr 07, 2025, 10:00 PM UTC
- investigating Apr 07, 2025, 09:40 PM UTC
Certain features on Coursera.org are currently unavailable, and we are working to resolve the issue.
- resolved Apr 07, 2025, 11:15 PM UTC
This incident has been resolved.
Notice December 16, 2024 Some interruptions on Coursera 3h 46m
Started Dec 16, 2024, 05:36 PM UTC· resolved Dec 16, 2024, 09:22 PM UTC
- investigating Dec 16, 2024, 05:36 PM UTC
Some learners are experiencing interruptions on Coursera. We are investigating and working to resolve.
- resolved Dec 16, 2024, 09:22 PM UTC
This incident has been resolved.