Lighthouse Outage History

Lighthouse is up right now

Lighthouse had 3 outages in the last 2 years totaling 79h 57m of downtime — averaging 0.1 incidents per month.

There were 3 Lighthouse outages since October 30, 2025 totaling 79h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.thetalententerprise.com

Major March 2, 2026

Ongoing AWS UAE Outage Impacting Media, File Uploads and Reports

Detected by Pingoru
Mar 02, 2026, 09:53 AM UTC
Resolved
Mar 05, 2026, 03:04 PM UTC
Duration
3d 5h
Timeline · 1 update
  1. resolved Mar 05, 2026, 03:04 PM UTC

    AWS services continue to improve following the recent outage. All lighthouse services have been fully restored and are now operational. We remain in close communication with AWS and are monitoring their official updates regarding the outage **Next Steps** - Continued monitoring of AWS service status and outage reports - Ongoing replacement of affected S3 images across our platform - We will provide further updates if any new issues emerge We appreciate your patience during this incident and thank you for your continued use of our services.

Read the full incident report →

Major October 30, 2025

Oracle Cloud outage in Jeddah KSA

Detected by Pingoru
Oct 30, 2025, 08:06 AM UTC
Resolved
Oct 30, 2025, 10:35 AM UTC
Duration
2h 29m
Timeline · 1 update
  1. resolved Oct 30, 2025, 10:35 AM UTC

    Update: Resolved **Status:** The Lighthouse is fully operational. Testing is complete and normal service has been restored for customers in the OCI Jeddah, KSA region. **What happened:** The outage appears to have been caused by an issue in the Oracle Cloud Infrastructure Jeddah region. We are still awaiting an official root cause from Oracle. **What we did:** Once the services from Oracle Cloud were accessible, we performed comprehensive verification tests, and confirmed system stability. **Customer impact:** No further disruption is expected. If you experience any issues, please report them immediately.

Read the full incident report →