Uptime.com Outage History

Uptime.com is up right now

Uptime.com had 27 outages in the last 2 years totaling 672h 59m of downtime — averaging 1.1 incidents per month.

There were 27 Uptime.com outages since March 28, 2026 totaling 672h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.uptime.com

Minor July 29, 2026

Connectivity Degraded - Netherlands-Amsterdam

Detected by Pingoru
Jul 29, 2026, 04:23 AM UTC
Resolved
Jul 29, 2026, 11:01 AM UTC
Duration
6h 37m
Timeline · 3 updates
  1. investigating Jul 29, 2026, 04:23 AM UTC

    We are currently experiencing connectivity issues affecting a few probe servers in our `Netherlands-Amsterdam` location. This may result in false positives, elevated latency, packet loss, or failed monitoring requests reported specifically from the Netherlands-Amsterdam monitoring location. Probe server/s affected: - ` NL-Amsterdam(IronMountain)-2` Our engineering team is investigating the issue and is working with the relevant provider to restore normal service as quickly as possible. We will share further updates as soon as more information becomes available. Should you require further assistance or have any questions, please do not hesitate to contact our support team.

  2. identified Jul 29, 2026, 05:05 AM UTC

    Our service provider has reported an ongoing infrastructure maintenance in their Amsterdam data centre, which is impacting some servers. Their networking team is actively working to complete the maintenance and restore service to the affected systems as soon as possible. We will continue to monitor the situation closely and provide updates as we receive them. Thank you for your patience and understanding.

  3. resolved Jul 29, 2026, 11:01 AM UTC

    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.

Read the full incident report →

Minor July 28, 2026

Intermittent DNS resolution timeouts for HTTP checks in APAC region

Detected by Pingoru
Jul 28, 2026, 12:00 PM UTC
Resolved
Jul 30, 2026, 05:18 AM UTC
Duration
1d 17h
Timeline · 5 updates
  1. investigating Jul 28, 2026, 12:00 PM UTC

    HTTP checks are intermittently failing at a few APAC probe locations with DNS lookup timeouts: ``` dial tcp: lookup on x.x.x.x:53: ... i/o timeout ``` Failures are intermittent. The trigger is confirmed, the underlying cause of the dropped/slow lookups is still under investigation. Affected locations: - Japan-Tokyo - Japan-Osaka - Australia-Sydney - Singapore-Singapore (unexpectedly affected; under investigation)

  2. monitoring Jul 29, 2026, 01:14 PM UTC

    The issue has been identified and addressed. We are currently monitoring the situation to ensure that checks recover and systems at the affected locations remain stable. The cause was a DNS resolver misconfiguration that led to occasional domain-name resolution failures, more frequently at geographically distant locations. This has been corrected.

  3. investigating Jul 29, 2026, 05:20 PM UTC

    The issue was only partially mitigated, while we see less domain resolution timeouts, it has not been solved completely. We are rolling out a patch to affected systems

  4. monitoring Jul 29, 2026, 06:09 PM UTC

    A change affected domains resolution configuration has been rolled back. All affected checks should recover shortly. This includes an increased response time from checks executed in affected locations. The system is being actively monitored and the incident will get resolved once we ensure that the issue has been properly addressed

  5. resolved Jul 30, 2026, 05:18 AM UTC

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

Read the full incident report →

Minor July 24, 2026

Degraded Performance Across Multiple Probe Locations

Detected by Pingoru
Jul 24, 2026, 10:55 AM UTC
Resolved
Jul 24, 2026, 12:05 PM UTC
Duration
1h 10m
Timeline · 1 update
  1. resolved Jul 24, 2026, 10:55 AM UTC

    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.

Read the full incident report →

Minor July 16, 2026

Location Down - Bolivia-La Paz

Detected by Pingoru
Jul 16, 2026, 06:00 PM UTC
Resolved
Jul 16, 2026, 10:15 PM UTC
Duration
4h 15m
Timeline · 3 updates
  1. identified Jul 16, 2026, 06:00 PM UTC

    We are currently facing connection issues with the `BO-La Paz(EdgeUno)-1` probe server. Our service provider is reporting an outage in their `La Paz - Bolivia` data centre. Our Engineering team is working closely with the provider to resolve the issue swiftly. 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.

  2. monitoring Jul 16, 2026, 06:57 PM UTC

    The `BO-La Paz(EdgeUno)-1` probe server is back Online and systems have started to stabilize. We will continue to monitor the probe server to ensure smooth operation and will collaborate with our service provider as necessary for more details.

  3. resolved Jul 16, 2026, 10:15 PM UTC

    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.

Read the full incident report →

Minor June 30, 2026

Application Performance Degradation

Detected by Pingoru
Jun 30, 2026, 12:54 AM UTC
Resolved
Jun 30, 2026, 05:42 AM UTC
Duration
4h 48m
Timeline · 3 updates
  1. investigating Jun 30, 2026, 12:54 AM UTC

    We are currently experiencing degraded application performance. Some users may encounter intermittent access issues or page errors on uptime.com. Our engineering team is investigating the issue and is actively working on a resolution. We are monitoring the situation closely and will provide updates as new 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 Jun 30, 2026, 04:55 AM UTC

    A fix has been deployed and systems have started to stabilize. We are continuing to closely monitor performance to confirm full stability before marking this incident as resolved. We will provide a further update once monitoring is complete. Thank you for your patience. If you have any questions or require assistance, please feel free to contact our support team.

  3. resolved Jun 30, 2026, 05:43 AM UTC

    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.

Read the full incident report →

Minor June 30, 2026

Decommissioning of Probe Server IP Addresses - 30 June 2026

Detected by Pingoru
Jun 30, 2026, 12:00 AM UTC
Resolved
Jul 07, 2026, 11:59 PM UTC
Duration
7d 23h
Timeline · 1 update
  1. monitoring Jun 30, 2026, 12:00 AM UTC

    As part of our ongoing infrastructure improvements, we are replacing probe servers across several regions. As a result, the following IP addresses will be retired and removed from the Uptime.com IP monitoring range list: - **US-CA-Fremont**: `173.255.240.87`|`2600:3c01::f03c:94ff:fe21:28d9` - **Chile-Santiago**: `64.176.9.55`|`2001:19f0:c800:2a5c:5400:04ff:fe5d:0da9` - **Japan-Osaka**: `64.176.48.147`|`2401:c080:3800:212f:5400:04ff:fe5d:0da1` ### **Action Required:** If you have configured firewall ACLs or allowlists that include any of the IP addresses above, please remove or update those rules starting **30 June 2026** to prevent unintended access policy conflicts. No action is required if you do not explicitly allowlist Uptime.com probe server IPs in your infrastructure. If you have any questions or need assistance, please don't hesitate to contact our support team.

Read the full incident report →

Minor June 26, 2026

Connectivity Degraded - US-NY-New York

Detected by Pingoru
Jun 26, 2026, 10:09 PM UTC
Resolved
Jun 27, 2026, 02:08 PM UTC
Duration
15h 59m
Timeline · 4 updates
  1. investigating Jun 26, 2026, 10:00 PM UTC

    We are currently experiencing connectivity issues affecting all probe servers in our `US-NY-New York` location. This may result in false positives, elevated latency, packet loss, or failed monitoring requests reported specifically from the `US-NY-New York` monitoring location. Probe servers affected: - `US-New York(DigitalRealty)-19` - `US-New York(DigitalRealty)-20` - `US-New York(DigitalRealty)-21` - `US-New York(DigitalRealty)-22` - `US-New York(DigitalRealty)-23` - `US-New York(DigitalRealty)-24` - `US-New York(DigitalRealty)-25` - `US-New York(DigitalRealty)-26` - `US-New York(DigitalRealty)-27` Our engineering team is investigating the issue and is working with the relevant provider to restore normal service as quickly as possible. We will share further updates as soon as more information becomes available. Should you require further assistance or have any questions, please do not hesitate to contact our support team.

  2. identified Jun 26, 2026, 11:15 PM UTC

    Our provider has implemented a fix for the connectivity issues affecting our `US-NY-New York` monitoring location. They are currently monitoring the results to confirm that service has fully stabilised. We will continue to monitor the location and will provide a further update once normal connectivity has been confirmed.

  3. monitoring Jun 27, 2026, 12:22 AM UTC

    We can confirm that the connectivity issue affecting our `US-NY-New York` monitoring location has been resolved. We will continue to monitor the location to ensure service remains stable.

  4. resolved Jun 27, 2026, 02:08 PM UTC

    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.

Read the full incident report →

Minor June 24, 2026

Location Down - Philippines-Manila

Detected by Pingoru
Jun 24, 2026, 08:24 PM UTC
Resolved
Jun 25, 2026, 01:58 AM UTC
Duration
5h 34m
Timeline · 2 updates
  1. investigating Jun 24, 2026, 08:24 PM UTC

    We are currently facing connection issues with the `PH-Manila(PLDT)-1` 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. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

  2. resolved Jun 25, 2026, 01:58 AM UTC

    We’re pleased to confirm that the connection issues with our `PH-Manila(PLDT)-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.

Read the full incident report →

Minor June 18, 2026

Connectivity Degraded - Turkey-Ankara

Detected by Pingoru
Jun 18, 2026, 02:31 PM UTC
Resolved
Jun 19, 2026, 12:11 AM UTC
Duration
9h 39m
Timeline · 2 updates
  1. identified Jun 18, 2026, 02:31 PM UTC

    We are experiencing connection issues with our probe servers in the `Turkey-Ankara` location. This is currently resulting in data packet loss and high latency rates of both inbound and outbound IPv6 traffic across multiple locations. Server/s affected: - `TU-Ankara(Turktelekom)-1` One of our service providers has reported to be experiencing routing issues resulting in a service degradation and/or packet loss in IPv6. 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 Jun 19, 2026, 12:11 AM UTC

    We’re pleased to confirm that IPv6 connectivity on the affected probe server has been fully restored and remains stable. The `Turkey-Ankara` 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 June 9, 2026

Check Metrics Collection Interruption

Detected by Pingoru
Jun 09, 2026, 04:00 PM UTC
Resolved
Jun 09, 2026, 05:30 PM UTC
Duration
1h 30m
Timeline · 1 update
  1. resolved Jun 09, 2026, 05:52 PM UTC

    We are retroactively updating our status page for transparency regarding a resolved metrics collection issue. Between 16:00 and 17:30 UTC, check metrics were not collected in our production environment. Checks continued to run during this period, but some response time and related metric data may be unavailable in the dashboard for the affected window. The issue was identified and resolved, and metrics collection has resumed. No further impact is expected.

Read the full incident report →

Minor June 8, 2026

Vault items not resolving on select monitoring locations

Detected by Pingoru
Jun 08, 2026, 05:20 PM UTC
Resolved
Jun 10, 2026, 07:10 PM UTC
Duration
2d 1h
Timeline · 3 updates
  1. investigating Jun 08, 2026, 05:20 PM UTC

    We are investigating an issue affecting checks using vault items on select monitoring locations recently updated as part of our Global Probe Server Expansion. Vault-backed values are not currently being resolved correctly on the affected locations. This may cause checks that rely on vault items, such as custom headers, credentials, or other check configuration fields, to fail incorrectly. The currently identified affected locations are: - Australia-Sydney - Chile-Santiago - Japan-Osaka - Japan-Tokyo - South Africa-Johannesburg - US-CA-Fremont Checks running from other monitoring locations are not currently known to be affected. As a temporary workaround, affected customers can select alternative monitoring locations where suitable. Our engineering team has identified the issue and is working on a fix. We will provide further updates as remediation progresses.

  2. identified Jun 09, 2026, 05:49 PM UTC

    We have identified the issue affecting vault item resolution on select monitoring locations. A fix has been prepared and is pending deployment. Once deployed, checks using vault-backed values should resume working as expected from the affected locations. As a temporary workaround, affected customers can continue to use alternative monitoring locations where suitable. We will provide a further update once the fix has been deployed and validated.

  3. resolved Jun 10, 2026, 07:10 PM UTC

    A fix has been deployed and validated. Checks using vault-backed values are now resolving correctly on the affected monitoring locations. We will continue to monitor for any further issues. Thank you for your patience while we worked to resolve this.

Read the full incident report →

Minor June 5, 2026

Connectivity Degraded - Telstra Global Transit

Detected by Pingoru
Jun 05, 2026, 05:36 PM UTC
Resolved
Jun 08, 2026, 05:18 PM UTC
Duration
2d 23h
Timeline · 2 updates
  1. investigating Jun 05, 2026, 05:36 PM UTC

    We are currently investigating intermittent network connectivity issues affecting some Asia based monitoring locations. Initial findings indicate the issue is related to Telstra Global transit and is affecting both IPv4 and IPv6 connectivity. Checks may only be affected when traffic is routed over this transit provider, which may result in intermittent timeouts or false positive alerts from specific monitoring locations. Our team is monitoring the situation and will provide further updates as needed.

  2. resolved Jun 08, 2026, 05:18 PM UTC

    The intermittent network connectivity issues affecting some Asia based monitoring locations have now been resolved. Connectivity over the affected Telstra Global transit routes has stabilised, and both IPv4 and IPv6 connectivity are operating normally. We will continue to monitor for any further issues. Thank you for your patience.

Read the full incident report →

Minor May 27, 2026

Location Down - Australia-Brisbane

Detected by Pingoru
May 27, 2026, 12:25 PM UTC
Resolved
May 27, 2026, 10:52 PM UTC
Duration
10h 27m
Timeline · 2 updates
  1. identified May 27, 2026, 12:25 PM UTC

    We are currently facing connection issues with the `AU-Brisbane(NextDC)-1` probe server. Our service provider is reporting an ongoing network connectivity interruption on their data centre, which is impacting some servers. Their networking team is actively working to resolve the issue and restore service to the affected systems as soon as possible. Our Engineering team is working closely with the provider to resolve the issue swiftly. 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.

  2. resolved May 27, 2026, 10:53 PM UTC

    We’re pleased to confirm that the connection issues with our `AU-Brisbane(NextDC)-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.

Read the full incident report →

Minor May 23, 2026

Connectivity Degraded - Australia-Perth

Detected by Pingoru
May 23, 2026, 12:56 AM UTC
Resolved
May 23, 2026, 05:00 PM UTC
Duration
16h 4m
Timeline · 2 updates
  1. identified May 23, 2026, 12:56 AM UTC

    We are experiencing connection issues with our probe servers in the `Australia-Perth` location. This is currently resulting in a complete loss of both inbound and outbound IPv4+IPv6 traffic across multiple locations. One of our server provider in the location has verified packet loss affecting international connectivity. Server/s affected: - `AU-Perth(Equinix)-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 May 23, 2026, 05:01 PM UTC

    IPv4+IPv6 connectivity to the `AU-Perth(Equinix)-1` probe server is UP and all systems are stable. The `Australia-Perth` 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 May 22, 2026

Connectivity Degraded - New Zealand-Auckland

Detected by Pingoru
May 22, 2026, 12:14 AM UTC
Resolved
May 22, 2026, 01:56 PM UTC
Duration
13h 42m
Timeline · 2 updates
  1. investigating May 22, 2026, 12:14 AM UTC

    We are experiencing connection issues with our probe servers in the `New Zealand-Auckland` location. This is currently resulting in data packet loss and high latency rates of both inbound and outbound IPv6 traffic across multiple locations. Server/s affected: - `NZ-New Zealand(DataCentre220)-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 May 22, 2026, 01:56 PM UTC

    We’re pleased to confirm that IPv6 connectivity on the affected probe server has been fully restored and remains stable. The `New Zealand-Auckland` 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 May 15, 2026

Connectivity Degraded - Taiwan-Taipei

Detected by Pingoru
May 15, 2026, 04:23 PM UTC
Resolved
May 15, 2026, 07:16 PM UTC
Duration
2h 52m
Timeline · 2 updates
  1. investigating May 15, 2026, 04:23 PM UTC

    We are experiencing connection issues with our probe server in the `Taiwan-Taipei` location. This is currently resulting in a complete loss of both inbound and outbound IPv6 traffic across multiple locations. Server/s affected: - `TW-Taipei(ChiefLY)-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 May 15, 2026, 07:16 PM UTC

    We’re pleased to confirm that IPv6 connectivity on the affected probe server has been fully restored and remains stable. The `Taiwan-Taipei` 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 May 4, 2026

Checks Degradation Due to Configuration Sync Issue

Detected by Pingoru
May 04, 2026, 03:31 PM UTC
Resolved
May 04, 2026, 07:44 PM UTC
Duration
4h 12m
Timeline · 3 updates
  1. identified May 04, 2026, 03:31 PM UTC

    We are currently experiencing an issue affecting all Checks across our platform. Multiple probe servers are unable to retrieve the latest check configuration updates, resulting in inconsistent or failed check execution. Our engineering team is aware of the problem and actively investigating the root cause. Work is underway to implement a fix and restore normal operation as quickly as possible. During this time, you may observe stale results, missing data, or unexpected check behavior. We recommend treating current check statuses with caution until the issue is resolved. We will continue to provide updates as more information becomes available. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

  2. monitoring May 04, 2026, 04:00 PM UTC

    A fix has been successfully deployed to address the issue affecting check configuration synchronization across probe servers. All probe servers are now in the process of stabilizing, and our engineering team is actively monitoring their performance to ensure check configurations are being retrieved and executed correctly. At this time, check results should begin returning to normal. However, brief inconsistencies may still be observed as systems fully recover. We will continue to monitor closely and provide further updates if necessary. Thank you for your patience and understanding.

  3. resolved May 04, 2026, 07:45 PM UTC

    The issue affecting check configuration synchronization across probe servers has been fully resolved. All probe servers are now operating normally and have successfully resumed retrieving the latest check configurations. Check execution and reporting have returned to expected behavior across the platform. Our engineering team has completed validation and will continue to monitor the environment to ensure ongoing stability. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

Read the full incident report →

Minor April 30, 2026

Connectivity Degraded - US-NV-Las Vegas

Detected by Pingoru
Apr 30, 2026, 01:00 PM UTC
Resolved
Apr 30, 2026, 11:41 PM UTC
Duration
10h 40m
Timeline · 3 updates
  1. investigating Apr 30, 2026, 01:00 PM UTC

    We are experiencing connection issues with our probe servers in the `US-NV-Las Vegas` location. This is currently resulting in a complete loss of inbound and outbound IPv4 traffic across multiple locations. Server/s affected: - `uptime-las01-versaweb.uptime.com` 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. identified Apr 30, 2026, 02:22 PM UTC

    Our service provider has reported ongoing network connection issues in their Las Vegas data centre, which is impacting some servers. Their networking team is actively working to resolve the issue and restore service to the affected systems as soon as possible. We will continue to monitor the situation closely and provide updates as we receive them. Thank you for your patience and understanding.

  3. resolved Apr 30, 2026, 11:43 PM UTC

    IPv4 access to the `US-Las Vegas(Fiberhub)-1` probe server is UP and all systems are 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.

Read the full incident report →

Minor April 10, 2026

Connectivity Degraded - Peru-Lima

Detected by Pingoru
Apr 10, 2026, 01:21 PM UTC
Resolved
Apr 10, 2026, 07:53 PM UTC
Duration
6h 32m
Timeline · 3 updates
  1. investigating Apr 10, 2026, 01:21 PM UTC

    We are experiencing connection issues with our probe servers in the `Peru-Lima` location. This is currently resulting in a complete loss of both inbound and outbound IPv4+IPv6 traffic across multiple locations. Server/s affected: - `PE-Lima(Cirion)-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. identified Apr 10, 2026, 02:28 PM UTC

    One of our service provider in the `Peru-Lima` location is experiencing an outage due to network connection issues in their data centre. Our engineering team is actively monitoring and collaborating with the provider to the status of this outage. We will share further updates as soon as more information becomes available. If you have any questions or need assistance, please contact our support team.

  3. resolved Apr 10, 2026, 07:53 PM UTC

    The `PE-Lima(Cirion)-1` probe server is back Online and systems have been stable. The `Peru-Lima` 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 April 10, 2026

Connectivity Degraded - Ukraine-Kiev

Detected by Pingoru
Apr 10, 2026, 05:48 AM UTC
Resolved
Apr 10, 2026, 04:41 PM UTC
Duration
10h 52m
Timeline · 3 updates
  1. investigating Apr 10, 2026, 05:48 AM UTC

    We are experiencing connection issues with our probe servers in the `Ukraine-Kiev` location. This is currently resulting in a complete loss of both inbound and outbound IPv4+IPv6 traffic across multiple locations. Server/s affected: - `UA-Kiev(Newtelco)-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. monitoring Apr 10, 2026, 01:56 PM UTC

    The `UA-Kiev(Newtelco)-1` probe server is back Online and systems have started to stabilize. We will continue to monitor the probe server to ensure smooth operation and will collaborate with our service provider as necessary for more details.

  3. resolved Apr 10, 2026, 04:41 PM UTC

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

Major April 9, 2026

Email Delivery Issues

Detected by Pingoru
Apr 09, 2026, 09:11 PM UTC
Resolved
Apr 10, 2026, 04:37 AM UTC
Duration
7h 25m
Timeline · 3 updates
  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

Detected by Pingoru
Apr 02, 2026, 04:20 PM UTC
Resolved
Apr 02, 2026, 06:33 PM UTC
Duration
2h 12m
Timeline · 3 updates
  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

Detected by Pingoru
Apr 02, 2026, 11:37 AM UTC
Resolved
Apr 03, 2026, 02:09 AM UTC
Duration
14h 31m
Timeline · 2 updates
  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 →