Uptime.com Outage History

Uptime.com degraded · 1 long-running issue View live status →

Pingoru has recorded 62 incidents for Uptime.com: 62 in the last 12 months and 32 in the last 90 days.

Source: status.uptime.com

62incidents recorded
62last 12 months
32last 90 days
40 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct7
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct43%
Pingoru began tracking Uptime.com in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026749 of 720 (7%)
May 20267112 of 744 (15%)
June 202611273 of 720 (38%)
July 20265239 of 744 (32%)
August 202614554 of 744 (74%)
September 20269249 of 720 (35%)
October 20267252 of 591 (43%)

Incidents, newest first

Major April 9, 2026 Email Delivery Issues 7h 25m

Started Apr 09, 2026, 09:11 PM UTC· resolved Apr 10, 2026, 04:37 AM UTC

  1. investigating Apr 09, 2026, 09:11 PM UTC

    We are currently experiencing issues with email delivery, including password reset emails, notifications, and status page communications. This is due to an issue with our email delivery provider. We are actively working to resolve the problem and restore normal email functionality as quickly as possible. We will provide further updates as more information becomes available.

  2. identified Apr 09, 2026, 11:00 PM UTC

    The issue affecting email delivery has been identified, and mitigation steps have been implemented. Email delivery remains impacted while we continue working with our provider to fully restore service. We are actively monitoring the situation and will provide further updates as progress continues.

  3. resolved Apr 10, 2026, 04:38 AM UTC

    The issue affecting email delivery has now been resolved, and all services are operating normally. We are continuing to monitor to ensure stability. We apologize for any inconvenience caused and appreciate your patience.

Read the full incident report →

Minor April 2, 2026 Check Configuration Propagation Delays Across Multiple Locations 2h 12m

Started Apr 02, 2026, 04:20 PM UTC· resolved Apr 02, 2026, 06:33 PM UTC

  1. investigating Apr 02, 2026, 04:20 PM UTC

    We are currently investigating an issue affecting the propagation of check configurations across multiple probe servers and locations. Newly created checks, as well as updates to existing checks, may not be reaching probe servers as expected. As a result, new checks may not start running and configuration changes may be delayed. Our engineering team is actively investigating the issue. We will provide further updates as soon as more information becomes available.

  2. monitoring Apr 02, 2026, 05:38 PM UTC

    We have identified the issue affecting check configuration propagation across multiple probe servers and locations. The problem was introduced by a recently deployed development change, which has now been reverted. We are currently running the reconfiguration process to ensure newly created checks and configuration updates are applied correctly across affected probe servers. We are actively monitoring recovery and verifying that checks are being reconfigured as expected. Further updates will be provided if needed.

  3. resolved Apr 02, 2026, 06:33 PM UTC

    The issue affecting check configuration propagation across multiple probe servers and locations has been resolved. A full reconfiguration has been completed and all checks and configuration updates are now being applied as expected. We will continue to monitor to ensure stability.

Read the full incident report →

Minor April 2, 2026 Connectivity Degraded - Italy-Milan 14h 31m

Started Apr 02, 2026, 11:37 AM UTC· resolved Apr 03, 2026, 02:09 AM UTC

  1. investigating Apr 02, 2026, 11:37 AM UTC

    We are experiencing connection issues with our probe servers in the `Italy-Milan` location. This is currently resulting in data packet loss and high latency rates of both inbound and outbound IPv4+IPv6 traffic across multiple locations. One of our service providers is experiencing network connectivity issues in their Milan data centre. Server/s affected: - ` IT-Milan(Telehouse)-1` Our engineering team is actively collaborating with the provider to resolve the problem as quickly as possible. We will share updates as soon as we have new information. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

  2. resolved Apr 03, 2026, 02:09 AM UTC

    We’re pleased to confirm that network connectivity on the `Italy-Milan` probe servers has been fully restored and remains stable. The `Italy-Milan` 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.

Read the full incident report →

Minor March 30, 2026 Connectivity Degraded - Canada-Toronto 26m

Started Mar 30, 2026, 09:47 AM UTC· resolved Mar 30, 2026, 10:13 AM UTC

  1. resolved Mar 30, 2026, 09:47 AM UTC

    Between 09:47 and 10:13 UTC, we experienced a networking issue affecting the `CA-Toronto(Cologix)-3` probe within our `Canada–Toronto` location, resulting in a loss of both IPv4 and IPv6 connectivity (inbound and outbound). During this time, some customers may have received false positive alerts from this probe. The issue was identified as a provider-side networking problem and has since been resolved. Connectivity has been fully restored, and we are no longer observing any impact. We are continuing to monitor closely.

Read the full incident report →

Minor March 28, 2026 Intermittent False Positive Alerts - Germany-Berlin 2d 9h

Started Mar 28, 2026, 01:00 AM UTC· resolved Mar 30, 2026, 10:00 AM UTC

  1. resolved Mar 28, 2026, 01:00 AM UTC

    We have completed our investigation into the recent degradation and identified the root cause as DNS related. During this time, some systems temporarily used upstream DNS resolvers provided by our infrastructure provider, which experienced issues over the weekend. This led to intermittent failures and some false positive alerts. As a mitigation, we have updated our systems to ensure our configured DNS resolvers are consistently enforced and not impacted by upstream configuration changes. We have not observed any further issues and consider this fully resolved.

Read the full incident report →