Is Uptime.com down?

We are currently experiencing an outage at the `US-NV-Las Vegas` location, specifically affecting the `US-Las Vegas(Fiberhub)-1` probe server. Our Engineering team is actively working with the provider to resolve this issue as quickly as possible. We will provide updates as soon as they become available. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

We are pleased to inform you that the `US-NV-Las Vegas` location is now stable and fully operational. Services have been restored, and all probe servers are functioning as expected. Thank you for your patience and understanding during this time.

Since October 29, 10:28 UTC, some checks from our `Singapore-Singapore`, `India-Bangalore`, `Australia-Melbourne` and `South Korea-Seoul` monitoring locations may not be running as expected. Customers may see missed or failed checks from these locations during this time. The cause is a network connectivity problem between these locations and our central monitoring systems. It is not caused by customer systems. Our engineering team has identified the problem and is working to restore normal service. We will share further updates as they become available. If you have any questions or need assistance, please contact our support team.

We're pleased to confirm that checks from our `Singapore-Singapore`, `India-Bangalore`, `Australia-Melbourne` and `Korea-Seoul` monitoring locations are running as expected again. Between 10:28 and 11:29 UTC on October 29, 2026, some checks from these locations may not have run as expected, and customers may have seen missed or failed checks during this period. The issue was caused by a network connectivity problem between these locations and our central monitoring systems. This issue was not caused by customer systems or configurations. Network connectivity has been restored, and our engineering team has confirmed that all checks from these locations are running normally. No action is required from customers. We apologize for any inconvenience caused. Thank you for your patience. If you experience any further issues, please feel free to reach out to our support team.

Between 11:35 and 13:10 UTC today, a change to how monitoring alerts are delivered caused some checks to remain marked as down after a brief failure, even once the monitored service had recovered. Affected checks may have sent down notifications and may still be showing as down. We rolled back the change at 13:10 UTC, so new results are being handled normally again. We are now clearing the checks that are still incorrectly showing as down. No action is needed on your side.

All checks affected by this issue have been reset and now reflect their current status. The change was rolled back at 13:10 UTC and alerting has been working normally since. Monitoring itself was not affected: our locations continued to run and record checks normally throughout. We apologise for the incorrect alerts and are reviewing our release process to prevent this from happening again.

Since October 26, 15:27 UTC, some checks from our `Australia-Sydney`, `Bulgaria-Sofia`, `Germany-Munich` and `Singapore-Singapore` monitoring locations may not be running as expected. Customers may see missed or failed checks from these locations during this time. The cause is a problem with the network equipment that connects our servers at these locations. It is not caused by customer systems. Our engineering team has identified the problem and is working to restore normal service, and some locations are already starting to recover. We will share further updates as they become available. If you have any questions or need assistance, please contact our support team.

Checks from our `Bulgaria-Sofia` and `Germany-Munich` monitoring locations have recovered and are running as expected. Some checks from our Australia-Sydney and Singapore-Singapore locations may still not be running as expected. Our engineering team is continuing to work on restoring normal service at these locations. We will share further updates as they become available. If you have any questions or need assistance, please contact our support team.

We're pleased to confirm that checks from our `Australia-Sydney`, `Bulgaria-Sofia`, `Germany-Munich` and `Singapore-Singapore` monitoring locations are running as expected again. Between 15:27 and 18:36 UTC on October 26, 2026, some checks from these locations may not have run as expected, and customers may have seen missed or failed checks during this period. The issue was caused by a problem with the network equipment that connects our servers at these locations. This issue was not caused by customer systems or configurations. Our engineering team has restored service and confirmed that all checks from these locations are running normally. No action is required from customers. We apologize for any inconvenience caused. Thank you for your patience. If you experience any further issues, please feel free to reach out to our support team.

We are currently facing connection issues with the `Default Test Server #2 - GB-London` probe server. Our Engineering team is working closely with the provider to resolve the issue swiftly. We will provide updates as soon as they become available. For the meantime, you may continue to use the `Default Test Server #1 - US-Central` test server. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

We have identified the cause of the connection issues with the `Default Test Server #2 - GB-London` probe server. Our service provider is performing emergency maintenance on the physical host supporting this probe server to apply a critical security patch. The probe server will be unavailable during the maintenance, which the provider expects to take 30 to 60 minutes. It will come back online automatically once the maintenance is complete. Our Engineering team is monitoring the situation closely with the provider and will confirm the probe server is fully operational once it is back online. We will provide updates as soon as they become available. In the meantime, you may continue to use the `Default Test Server #1 - US-Central` test server. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

The `Default Test Server #2 - GB-London` probe server remains unavailable. The emergency maintenance by our service provider on the physical host supporting this probe server is taking longer than initially expected. Our Engineering team has followed up with the provider and is working with them to bring the probe server back online as soon as possible. We will provide updates as soon as they become available. In the meantime, you may continue to use the `Default Test Server #1 - US-Central` test server. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

The `Default Test Server #2 - GB-London` probe server is back online following the completion of our service provider's emergency maintenance, and systems have started to stabilize. Our Engineering team will continue to monitor the probe server closely to ensure smooth operation. We will provide a final update once we have confirmed the issue is fully resolved. In the meantime, should you experience any issues with this test server, you may continue to use the `Default Test Server #1 - US-Central` test server. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

We're pleased to confirm that the connection issues with our `Default Test Server #2 - GB-London` probe server have been resolved. Our service provider has completed the emergency maintenance, and the probe server is back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity. If you experience any further issues, please reach out to our support team.