Störungsverlauf von Isdown

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

Systems seems to be back to normal, but we will continue to monitor the situation

This incident has been resolved.

We're getting reports that website monitors might be triggering down alerts. We're investigating possible causes.

We've made some changes and will monitor the fix for the next few hours

The issue seems to be with our North America server that runs the checks. We're still trying to understand the root cause.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We've identified a situation where some background jobs (monitors and notifications) got stuck in the queues and were only processed when we released the fix. We're sorry for the issues caused.

We've released a fix, and now queues are being processed.

This incident has been resolved.

We are currently investigating this issue.

The issue is related to an outage in one of our upstream providers (Cloudflare) https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

It seems we're back online. We'll keep this incident open until resolution is confirmed.

This incident has been resolved.

There's an ongoing outage with Cloudflare that affects access to IsDown for some users. More details in https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

This might also impact the monitoring of third-party services for status pages that are behind Cloudflare.

Cloudflare says we issue is now fixed, and we're seeing improvements.

This incident has been resolved.

The source we use to get Azure official outages is currently unavailable. We're trying to find ways to get the information. Sorry for the situation.

We've found an alternate way and we're implementing the fix

This incident has been resolved.

There's an ongoing AWS outage that affects a great part of the internet, and especially one big status page provider where we collect the data. We're going through the queue as it seems to be recovering. Sorry for the delay.

This incident has been resolved.

We've identified an issue that occurred over the last 24-48 hours with our Asia-based probe, which may cause problems with uptime monitoring detection.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

The website is now accessible again. We will continue to monitor to understand if it fully recovered.

This incident has been resolved.

We are currently investigating issues with the North American servers responsible for testing the uptime of custom monitors.

The issue is related to a problem with our cloud provider (https://status.digitalocean.com/incidents/ndhzmhvjpy80), and we’re trying to determine if there is a workaround.

We continue to monitor the situation and are working to find a workaround. In the meantime, we have disabled the North America region to prevent false positives.

This incident has been resolved.

From around 00:30 a.m. UTC to 03:40 a.m. UTC, we had an issue with the servers used to monitor the North American region, creating false positives.

The incident has been resolved. We sincerely apologize for the situation and will take the necessary steps in the next few days to prevent a recurrence.

We're getting reports of timeouts similar to those in a previous incident (https://isdown.statuspage.io/incidents/3h2h83sd1bjg). We're checking with the cloud provider to see if there is anything we can do to mitigate the situation. Monitoring and Notifications are not affected.

This incident has been resolved.

We are currently investigating this issue.

It's an issue with our cloud provider. We're trying to understand what could be a solution to this problem.

We continue to see with Heroku what possible options to mitigate the situation (https://status.heroku.com/incidents/2684). The current situation is that requests will get a connection timeout.

We’re seeing some improvements with far fewer timeouts. We’ll keep monitoring.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

Our system sent recovery notifications to monitors that were already operational. We've deployed a fix. We're sorry for the issue. Please let us know if you have any questions.

Our provider is having problems with servers in Asia. We've disabled the check from this location, and continue to monitor the situation so we can re-enable it as soon as possible.

We are continuing to work on a fix for this issue.

This incident has been resolved.

We're working with the third-party provider to fix this quickly.

This incident has been resolved.

We are currently having issues with a status page provider, which may cause some delays in getting the latest information.

We're seeing recovery of the system. We're going to continue to monitor.

This incident has been resolved.