Historical record of incidents for IsDown
Report: "IsDown is currently unacessible"
Last updateWe are currently investigating this issue.
Report: "IsDown.app is current inaccessible"
Last updateThis incident has been resolved.
The website is now accessible again. We will continue to monitor to understand if it fully recovered.
We are currently investigating this issue.
Report: "Issue with Custom Monitors in the North America Region"
Last updateThis incident has been resolved.
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.
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 are currently investigating issues with the North American servers responsible for testing the uptime of custom monitors.
Report: "Issue with servers used for custom monitoring in the North America region"
Last updateThe 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.
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.
Report: "Multiple reports of timeouts accessing isdown.app"
Last updateThis incident has been resolved.
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.
Report: "Multiple reports of timeouts accessing isdown.app"
Last updateThis incident has been resolved.
We’re seeing some improvements with far fewer timeouts. We’ll keep monitoring.
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.
It's an issue with our cloud provider. We're trying to understand what could be a solution to this problem.
We are currently investigating this issue.
Report: "Wrongly notifications sent for SSL Monitors"
Last updateOur 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.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Issues with Asia checks"
Last updateThis incident has been resolved.
We are continuing to work on a fix for this issue.
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.
Report: "Email provider is having issues and email notifications are delayed"
Last updateThis incident has been resolved.
We're working with the third-party provider to fix this quickly.
Report: "Possible delays in getting latest outage information"
Last updateThis incident has been resolved.
We're seeing recovery of the system. We're going to continue to monitor.
We are currently having issues with a status page provider, which may cause some delays in getting the latest information.
Report: "Custom Monitors are not running"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "Problems with Datadog integration"
Last updateThis incident has been resolved.
Datadog calls stop giving an error. We will continue to monitor the situation and will wait until Datadog confirms the resolution to mark it as resolved.
We're having issues with sending data to Datadog. An outage in Datadog itself causes this. You can check more details in https://isdown.app/integrations/datadog/incidents/254163-elevated-error-rates-for-metrics-submission. We'll be monitoring the situation.
Report: "IsDown.app is inaccessible."
Last updateWe're back online. Seems it was a Cloudflare issue.
We are currently investigating this issue.
Report: "We're having some problems monitoring some status pages - Issue with third-party provider"
Last updateThis incident has been resolved.
Everything seems to be working correctly now. We will continue to monitor before closing the incident.
We are continuing to investigate this issue.
This is due to an ongoing incident with a status page provider.
Report: "We're having some delays monitoring some status pages"
Last updateThis incident has been resolved.
It seems it is recovering, but we will continue to monitor it.
The third-party status page has some degradation performance, which delays the response times.
Report: "We're upgrading our infrastructure"
Last updateThe upgrade was successful. We will continue to monitor to make sure everything is working as expected.
We're currently upgrading one database to better serve our customers.
Report: "AWS integration is being restructured & updated"
Last updateWe've wrapped up the integration. Nevertheless, we'll continue to monitor it closely.
We are continuing to monitor for any further issues.
AWS integration is back online. We're continuing to work and monitor to ensure it's 100%.
Our integration with the AWS status page is currently disabled since the communication structure with AWS changed. We're updating the integration so it goes live and starts monitoring AWS again ASAP.
Report: "IsDown.app is down"
Last updateWe're back online! Thank you for your patience!
Heroku is having an outage (https://status.heroku.com/incidents/2554) that impacts the IsDown website. We're sorry for the impact caused. Monitoring and Notifications continue to work as expected.
It's a problem with the Heroku router. We're reaching out to them to fix the issue.
Monitors and notifications are operational, but website and API are still down.
We are currently investigating this issue.
Report: "There are reports of multiple emails being received for service recovery"
Last updateThis incident has been resolved.
It seems the issue only affected customers that are monitoring Slack service. They got 5 extra recovery notifications (we're sorry for the noise). We've disabled the Slack status page monitoring while we understand the issue.
We are currently investigating this issue.
Report: "Third-party service (Atlassian Statuspage) is having performance issues that impacts our ability to monitor services with that provider"
Last updateThis incident has been resolved.
We are continuing to monitor for any further issues.
It seems the service is recovering, and we will continue to monitor.
There's an ongoing outage with Atlassian Statuspage (https://metastatuspage.com/incidents/wbc8bk75lg1j), which impacts our ability to monitor the services that use that provider.
The issue has been identified.
Report: "Delay delivering email notifications"
Last updateThis incident has been resolved.
We’re having an issue with our third party provider which is causing a delay in email notifications. We already contacted the provider to try to get it fixed ASAP. A workaround is set another notification channel.
Report: "Algorithm change to improve detection of outage severity trigger new notifications"
Last updateThis incident has been resolved.
Customers might have received notifications in bulk because the algorithm changed to improve major outage detections. Previous outages marked as minor changed to major, and notifications were sent according to customers' settings. We should have communicated the change previously to prevent any surprises. We're sorry for the trouble caused.
Report: "Duplicated notications in Azure"
Last updateWe've had an incident this morning regarding duplicated notifications around the same outage. We've now pushed a fix to prevent the issue.
Report: "Failed to send notifications for one incident in Azure"
Last updateThis incident has been resolved.
The problem was when there was a service with multiple ongoing outages going. Notifications weren't being sent for later ones. We've now deployed a fix to prevent this issue from happening again.
We are continuing to investigate this issue.
This morning we failed to send an outage notification related to Azure. We're looking into the issue to understand the possible problem and prepare a fix. We're sorry for the problems caused.
Report: "Customers can't create new connections from IsDown to PagerDuty"
Last updateThis incident has been resolved.
The installation flow between IsDown and PagerDuty is broken, and new connections can't be created. Old connections continue to work as expected. The issue is on the PagerDuty side, and we've already contacted PagerDuty support for feedback and resolution.
Report: "Fastly current status and outages currently unavailable"
Last updateThis incident has been resolved.
We are continuing to work on a fix for this issue.
Fastly changed their status page, and we're currently upgrading the integration. In the meantime, we're not able to monitor Fastly.
Report: "Faulty Deployment made the app unavailable for 2 minutes"
Last updateThis incident has been resolved.
Report: "False positive in Stripe"
Last updateSome customers got a notification about Stripe going through an outage. It was a false positive. We're sorry for the false alert.
Report: "Application isn't loading"
Last updateThis incident has been resolved.
3rd party database provider recovered from the issue. We'll continue to monitor it to make sure it's stable.
We are currently investigating this issue.