Open LMS Outage History

Started Oct 21, 2026, 01:41 PM UTC· resolved Oct 21, 2026, 10:53 PM UTC

1. identified Oct 21, 2026, 01:41 PM UTC

   What is happening: Open LMS is taking all customer sites offline within the next few minutes. Why: Two critical zero-day vulnerabilities in PHP have been discovered and are being actively exploited. No mitigation is currently available, so taking sites offline is the only way to fully protect them. These vulnerabilities affect PHP-based websites worldwide and are not specific to Open LMS. What's next: The PHP project expects to release patches today. As soon as they are available, we will apply them and bring sites back online. openlms.zendesk.com/hc/en-us/articles/31214374861084

2. identified Oct 21, 2026, 03:31 PM UTC

   Open LMS has taken all customer sites offline as a preventative measure. Why: Two critical zero-day vulnerabilities in PHP have been discovered and are being actively exploited. No mitigation is currently available, so taking sites offline is the only way to fully protect them. These vulnerabilities affect PHP-based websites worldwide and are not specific to Open LMS. What's next: The PHP project expects to release patches today. As soon as they are available, we will apply them and bring sites back online. openlms.zendesk.com/hc/en-us/articles/31214374861084

3. identified Oct 21, 2026, 06:02 PM UTC

   Thank you for your patience during this global security event. Patches for the PHP issues are beginning to be received, although there are several packages for each of the many versions of PHP that we run. We are actively updating all sites with the patches as they are ready but will not be restoring a service until that site is fully patched. We don't have a clear timeframe on when the full set of patches will be completed, but we are actively moving towards the goal. We will continue to provide updates as we make progress.

4. monitoring Oct 21, 2026, 08:01 PM UTC

   Sites are coming back online. PHP security patches are now available, and we are installing them across our hosting environment. We have begun restoring sites as each one is fully patched, and we expect restoration to continue over the next several hours. What this means for you If your site is back online, it has been patched against both PHP vulnerabilities. If your site is still offline, it is in the queue. You don’t need to do anything. We’ll restore it as soon as its patches are installed. We’ll keep posting updates here as restoration progresses. Thank you for your continued patience.

5. monitoring Oct 21, 2026, 10:40 PM UTC

   The overwhelming majority of customer sites are now fully patched and back online. We are actively working on the remaining sites and expect to restore them within the next few hours. Thank you for your patience and understanding throughout today’s event.

6. resolved Oct 21, 2026, 10:53 PM UTC

   This incident has been resolved. Please contact support if you have further questions or issues.

Read the full incident report →

Started May 08, 2026, 02:08 AM UTC· resolved May 09, 2026, 03:42 AM UTC

1. monitoring May 08, 2026, 02:08 AM UTC

   We are experiencing service interruptions caused by an AWS operational issue in some regions. Our team is engaged and will share updates as available.

2. monitoring May 08, 2026, 03:57 AM UTC

   Open LMS Cloud Services Infrastructure team have performed some mitigating actions to alleviate the impact of the upstream provider. Sites impacted should start seeing improvements.

3. monitoring May 08, 2026, 06:36 AM UTC

   The upstream provider are observing early signs of recovery and are continuing their efforts to restore services.

4. monitoring May 08, 2026, 06:58 PM UTC

   Our upstream provider is still working hard to get things back on track, but they’ve estimated that it might take a few more hours to fully recover. We continue to monitor progress and will provide updates as we have them.

5. resolved May 09, 2026, 03:42 AM UTC

   AWS has reported the underlying issue to be resolved. Based on close monitoring of our sites we have confirmed that services have stabilized.

Read the full incident report →

Started Oct 20, 2025, 12:54 PM UTC· resolved Oct 21, 2025, 08:40 AM UTC

1. monitoring Oct 20, 2025, 12:54 PM UTC

   We are experiencing service interruptions caused by an AWS outage in some regions. Our team is engaged and will share updates as available.

2. monitoring Oct 20, 2025, 02:14 PM UTC

   AWS continues to report progress on recovery efforts. We are manually adding resources and working to restore instances to a healthy state where possible. Full resolution will depend on AWS recovery.

3. monitoring Oct 20, 2025, 04:20 PM UTC

   AWS has narrowed down the cause of the ongoing outage and is taking mitigation steps. As a note: this is a widespread issue affecting multiple platforms, applications, and companies. We continue to monitor closely and are taking measures on our side to help stabilize impacted instances.

4. monitoring Oct 20, 2025, 08:16 PM UTC

   We’re continuing to support clients through the AWS outage. Many sites are showing improvement and some have recovered, but AWS is still actively working on the incident. We remain engaged and are monitoring closely.

5. monitoring Oct 20, 2025, 11:48 PM UTC

   As we move into the evening hours for those affected, rest assured our other regional teams are online and will remain attentive in case conditions change overnight. Most sites have recovered, but we’ll keep the incident open until AWS confirms full resolution.

6. resolved Oct 21, 2025, 08:40 AM UTC

   AWS has reported the underlying issue as resolved. Based on close monitoring of our sites we can confirm that services have stabilized.

Read the full incident report →