Uptime.com incident
Russia-Moscow Monitoring Location Decommissioning
Uptime.com experienced a minor incident on June 18, 2026, lasting 1h. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring Jun 11, 2026, 03:59 PM UTC
Our upstream infrastructure provider has postponed the planned decommissioning work for their Russia infrastructure presence. The maintenance window has moved from 11 June 2026 to 18 June 2026. The scheduled times remain unchanged. As a result, we are extending the deadline for customers to move checks away from the **Russia-Moscow** monitoring location. Customers with checks currently using **Russia-Moscow** should now update those checks to use an alternative monitoring location before 18 June 2026 at 20:00 UTC. After this time, **Russia-Moscow** will no longer be available, and checks will no longer run from this location. Checks using multiple monitoring locations will continue to run from their remaining configured locations. A list of available monitoring locations can be found here: [https://uptime.com/probe-server-locations](https://uptime.com/probe-server-locations) Please contact [[email protected]](mailto:[email protected]) if you have any questions.
- monitoring Jun 11, 2026, 08:00 PM UTC
Our upstream infrastructure provider has notified us that they are decommissioning their Russia infrastructure presence. As a result, we will be retiring the **Russia-Moscow** monitoring location. Reliable provider coverage in the region has become increasingly limited, and we do not plan to replace the **Russia-Moscow** monitoring location at this time. Customers with checks currently using **Russia-Moscow** should update those checks to use an alternative monitoring location before **11 June 2026 at 20:00 UTC**. A list of available monitoring locations can be found here: [https://uptime.com/probe-server-locations](https://uptime.com/probe-server-locations) After this time, **Russia-Moscow** will no longer be available, and checks will no longer run from this location. Checks using multiple monitoring locations will continue to run from their remaining configured locations. Please contact [[email protected]](mailto:[email protected]) if you have any questions. We apologise for any inconvenience caused.