Uptime.com incident

Intermittent Platform Service Disruption

Minor Resolved

Uptime.com experienced a minor incident on August 9, 2026, lasting 22d 6h. The incident has been resolved; the full update timeline is below.

Started
Aug 09, 2026, 09:15 AM UTC
Resolved
Aug 31, 2026, 03:56 PM UTC
Duration
22d 6h
Detected by Pingoru
Aug 09, 2026, 09:15 AM UTC

Update timeline

  1. investigating Aug 09, 2026, 09:15 AM UTC

    We experienced a brief period of intermittent service disruption affecting multiple Uptime.com services. During this time, some users experienced connection timeouts or were unable to access affected services. Service has now recovered, and we are monitoring closely to ensure continued stability. We are reviewing the incident internally and will implement any necessary follow-up actions. We apologize for any inconvenience caused.

  2. monitoring Aug 09, 2026, 10:36 AM UTC

    Affected services have resumed and are currently operating normally. We are continuing to monitor the platform closely while we investigate the cause of the disruption.

  3. monitoring Aug 09, 2026, 12:05 PM UTC

    Services have recovered and are currently operating normally. We identified database lock contention related to bulk scheduled maintenance operations as a contributing factor to the disruption. As a precaution, we have temporarily disabled the bulk scheduled maintenance API endpoint while we continue investigating and implementing additional safeguards. All other platform functionality remains available, and we are continuing to monitor closely for stability.

  4. monitoring Aug 11, 2026, 03:14 PM UTC

    Services have remained stable since our last update, and all monitoring functionality is operating normally. The bulk scheduled maintenance API endpoint remains temporarily disabled while we implement additional safeguards and fixes addressing the database lock contention identified as a contributing factor. All other platform functionality remains fully available. Thank you for your patience. If you experience any further issues, please reach out to our support team.

  5. resolved Aug 31, 2026, 03:56 PM UTC

    This incident is now Resolved. The safeguards and fixes addressing the database lock contention have been implemented, and the bulk scheduled maintenance API endpoint has been re-enabled. All API monitoring and functionality is operating normally. Thank you for your patience. If you continue to experience any issues, please contact our support team.