Uptime.com incident

Decommissioning of Probe Server IP Addresses - 30 June 2026

Minor Resolved

Uptime.com experienced a minor incident on June 30, 2026, lasting 7d 23h. The incident has been resolved; the full update timeline is below.

Started
Jun 30, 2026, 12:00 AM UTC
Resolved
Jul 07, 2026, 11:59 PM UTC
Duration
7d 23h
Detected by Pingoru
Jun 30, 2026, 12:00 AM UTC

Update timeline

  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.