Uptime.com incident

Intermittent Disruption Affecting Check Execution

Minor Resolved

Uptime.com experienced a minor incident on August 19, 2026, lasting 4h 35m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2026, 08:09 PM UTC
Resolved
Aug 20, 2026, 12:45 AM UTC
Duration
4h 35m
Detected by Pingoru
Aug 19, 2026, 08:09 PM UTC

Update timeline

  1. investigating Aug 19, 2026, 08:09 PM UTC

    We are experiencing intermittent service disruption affecting Uptime.com checks. A subset of checks may execute inconsistently or return inaccurate results during this period. We have identified the cause as a recent production release. Our engineering team is actively mitigating the impact and is preparing a corrective patch for deployment. Monitoring data and alerting for affected checks may be incomplete for the duration of this incident. No other platform services are currently impacted. We are treating this issue with high priority and will continue to provide updates as our investigation progresses and additional information becomes available. If you have any questions or require assistance, please feel free to contact our support team. We apologize for any disruption this may cause.

  2. monitoring Aug 19, 2026, 11:05 PM UTC

    Our engineering team has deployed a corrective patch addressing the issue introduced by the recent production release. Check execution has returned to expected behavior, and we are no longer observing inconsistent results across affected checks. We are continuing to monitor platform stability closely to confirm the fix holds under normal production load. Checks that failed to execute during the disruption window may show gaps in historical data. We will confirm full resolution once we have validated sustained normal operations. Thank you for your continued patience.

  3. resolved Aug 20, 2026, 02:46 AM UTC

    This incident is now resolved. Check execution has returned to expected behavior, and we are no longer observing inconsistent results across affected checks. The corrective patch addressing the issue introduced by the recent production release has been deployed and validated under normal production load. Thank you for your patience. If you continue to experience any issues, please contact our support team.