The last time Hackerfall tried to access this page, it returned a not found error. A cached version of the page is below, or clickhereto continue anyway

Pingdom Status - Major routing issues on the Internet

The Outage

A backbone carrier misconfigured something, causing routing issues for a lot of the world. More details here and at CloudFlare's status page here.

How did it affect Pingdom services?

Pingdom probe servers from around the world could not send data to us to alert in a timely manner. This coupled with the huge increase in the number of outages reported and subsequent alerts sent out caused delays.

Simplified and Basic alerting experienced some short delays whereas the less commonly used BeepManager alerts were significantly delayed, in some cases up to 20 minutes.

The huge number of outages reported simultaneously, along with My Pingdoms reliance on Cloudflare resulted in access troubles on My Pingdom, and a general slowdown of the service for the duration of the incident.

What will we do to remedy this?

In the face of the recent huge outages (DynDNS outage in October 2016), we are working on rebuilding the core of our alerting and reporting to mitigate the impact huge internet outages has on our service. We can of course not promise 100% uptime on our service since we are on the internet after all, but were working on making things better.

Continue reading on status.pingdom.com