IsDown Outage History

IsDown experienced a major incident affecting background job processing and causing timeouts across their monitoring services for both custom and third-party services, as well as their API. The issue lasted 38 minutes before a fix was implemented and the incident was resolved after monitoring confirmed the solution was effective.

IsDown experienced a major incident with background job processing that affected both custom services and third-party services monitoring for 2.5 hours. The issue impacted the platform's ability to process monitoring tasks for these services. The incident was resolved after systems returned to normal operation and continued monitoring confirmed stability.

IsDown's website monitoring service experienced a major incident where monitors were triggering false down alerts for 17.8 hours. The issue was traced to problems with the North America server responsible for running website checks. The service implemented a fix and monitored the results before fully resolving the incident.

IsDown experienced a major incident where background jobs for monitors and notifications became stuck in processing queues for 10 minutes. This affected multiple notification channels including webhooks, email, Slack, Discord, Microsoft Teams, Google Chat, Zapier, Datadog, and PagerDuty integrations. The issue was resolved by releasing a fix that restored normal queue processing.