Uptime.com Outage History

The system has stabilized.

We’re pleased to confirm that the connection issues with our `PR-San Juan(EdgeUno)-1` probe server have been resolved. All systems are back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity.

We’re pleased to confirm that the connection issues with our `PH-Manila(PLDT)-1` probe server have been resolved. All systems are back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity.

An API check has been optimized to work more efficiently with complex logic

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.

A network configuration has been updated. SMTP checks are back to normal

Between 11:18 and 14:50 GMT on August 17, an issue in our platform interrupted the collection of historical performance metrics. Check execution and alerting were not affected. All checks continued to run on schedule and alerts were delivered normally throughout this period. Performance metrics recorded during the affected window were not stored and cannot be recovered. Customers will see a gap in metrics charts and reports covering this time range. The issue is fully resolved and metrics collection is operating normally. We have made changes to prevent this from recurring. Uptime and downtime records, including SLA calculations, are unaffected.

We have doubled capacity of our scheduling layer to keep up with an increasing load of active check runs. The system is back to normal

We’re pleased to confirm that IPv4 and IPv6 network connectivity on the `US-Las Vegas(Fiberhub)-1` probe server has been fully restored and remains stable. The `US-NV-Las Vegas` location is now fully operational and network connectivity is normal. Thank you for your patience. If you experience any further issues, please reach out to our support team.

We’re pleased to confirm that the connection issues with our `NO-Oslo(IPOnly)-2` probe server have been resolved. All systems are back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity.

During a routine deployment, an internal message queue reached its storage capacity, which temporarily prevented performance metrics from being recorded. Approximately 2.5 hours of historical performance data (response times and related data points visible in check performance graphs) were not captured and cannot be backfilled. Check execution, uptime monitoring, and alerting were not affected at any point during this incident — all checks continued to run and alerts were delivered normally. The metrics recording pipeline has been fully restored. All systems are operating normally and performance metrics are being recorded as expected. We are implementing additional safeguards to prevent this class of issue from recurring.

We’re pleased to confirm that the connection issues with our `TW-Taipei(ChiefLY)-1` probe server have been resolved. All systems are back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity.

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.

We’re pleased to confirm that the connection issues with our `PA-Panama City(Movistar)-1` probe server has been resolved. All systems are back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity.

We’re pleased to confirm that network connectivity on the `NL-Amsterdam(IronMountain)-2` probe server has been fully restored and remains stable. The `Netherlands-Amsterdam` location is now fully operational and network connectivity is normal. Thank you for your patience. If you experience any further issues, please reach out to our support team.

The issue has been resolved, no new false positives have been seen since yesterdays update

We have completed our investigation and confirm that the intermittent network connectivity issues affecting a subset of our monitoring probe locations have been resolved. Our Engineering team identified the root cause as instability on Twelve99 transit routes serving the affected locations. Connectivity over these routes has since stabilised, and both IPv4 and IPv6 connectivity are now operating normally across all previously affected probes. All monitoring locations are fully operational, and check execution has returned to normal across the network. No further action is required from customers. We apologize for any inconvenience this may have caused. Should you have any questions or continue to observe anomalies, please contact our support team.

We’re pleased to confirm that network connectivity on all affected probe server has been fully restored and remains stable. The `Bolivia-La Paz` location is fully operational and network connectivity is normal. Thank you for your patience. If you experience any further issues, please reach out to our support team.

Application performance has remained stable following the earlier period of degraded performance and intermittent availability issues. We are marking this incident as resolved. We have reviewed the incident internally and will implement any necessary follow-up actions. We apologize for any inconvenience caused.

We’re pleased to confirm that network connectivity on all affected probe server has been fully restored and remains stable. The `US-NY-New York` location is now fully operational and network connectivity is normal. Thank you for your patience. If you experience any further issues, please reach out to our support team.