Categories
Announcements

False positives in EU monitoring region: what happened and what we’re doing about it. 

On Friday, a significant volume of users experienced false downtime alerts for monitors from our EU monitoring region. After investigation, we identified the root causes and have taken immediate steps to address them. 

What caused the incident?

  • Monitoring of decommissioned endpoints

Our systems continued to actively monitor endpoints that no longer exist or have been decommissioned. This included certain BGPs that are no longer announced, causing our monitoring activities to be perceived as indiscriminate network scanning by one of our hosting providers, leading to blocked traffic.

  • Regional impact

The combination of these factors led to a 45% drop in our available capacity in the EU region, making it more likely for monitoring delays or failures to trigger false positives.

How we’re fixing it:

  • Retiring monitoring on dormant endpoints: We are rolling out logic to stop monitoring endpoints from long-abandoned accounts.

  • Network expansion: We’re expanding our infrastructure in the EU and globally by partnering with additional providers. This will increase our monitoring capacity and redundancy, and reduce the risk of regional outages.

  • New IP addresses: We are introducing new IPs for our EU region. To ensure uninterrupted monitoring, we ask all users to whitelist our latest IPs before September 1, 2025 (with similar updates coming to other regions as well).

  • API for IP management: You can now automatically stay updated using our new IP API.

  • False alert cleanup: As part of our mitigation, all connection timeout incidents from the affected period will be removed from user accounts to clean up inaccurate reports.

  • SMS credits refund: All SMS and voice alert credits used during the August 1st, 2025, incident period will be refunded to your account.

Looking ahead

We take stability and reliability extremely seriously. We’re deeply committed to delivering accurate uptime monitoring, and this incident has already triggered key improvements across our infrastructure. We’re actively working to prevent similar issues from happening again.

Thanks for your trust and your patience.

The UptimeRobot Team

 


Written by Tomas Koprusak

Product Owner | LinkedIn

Tomas Koprusak is a Product Owner at UptimeRobot. He has a rich history in similar roles at global IT powerhouses like IBM, where he started as a developer and moved to a Product Manager position, working with EMEA clients and colleagues from the US, Brazil, and China.

Write for UptimeRobot

Join our External Writers Program and share your know-how with the global UptimeRobot community. Craft practical monitoring tutorials, earn competitive payouts for every accepted article, and let us deliver your insights to the readers who need them most.

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Articles