IsDown Outage History

IsDown is up right now

IsDown had 10 outages in the last 2 years totaling 26h 27m of downtime — averaging 0.4 incidents per month.

There were 10 IsDown outages since August 31, 2025 totaling 26h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://isdown.statuspage.io

Major April 21, 2026

Issues processing background jobs and some timeouts

Detected by Pingoru
Apr 21, 2026, 08:01 PM UTC
Resolved
Apr 21, 2026, 08:36 PM UTC
Duration
34m
Affected: Monitors ( Third-party services )Monitors ( Websites )API
Timeline · 3 updates
  1. investigating Apr 21, 2026, 08:01 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 21, 2026, 08:27 PM UTC

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

  3. resolved Apr 21, 2026, 08:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 14, 2026

Issues processing background jobs

Detected by Pingoru
Apr 14, 2026, 03:10 PM UTC
Resolved
Apr 14, 2026, 05:34 PM UTC
Duration
2h 24m
Affected: Monitors ( Third-party services )Monitors ( Websites )
Timeline · 3 updates
  1. investigating Apr 14, 2026, 03:10 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 14, 2026, 03:36 PM UTC

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

  3. resolved Apr 14, 2026, 05:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 24, 2026

Website Monitors might be triggering false alerts

Detected by Pingoru
Mar 24, 2026, 08:16 PM UTC
Resolved
Mar 25, 2026, 02:01 PM UTC
Duration
17h 44m
Affected: Monitors ( Websites )
Timeline · 6 updates
  1. investigating Mar 24, 2026, 08:16 PM UTC

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

  2. monitoring Mar 24, 2026, 08:37 PM UTC

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

  3. investigating Mar 24, 2026, 11:50 PM UTC

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

  4. investigating Mar 25, 2026, 07:14 AM UTC

    We are continuing to investigate this issue.

  5. monitoring Mar 25, 2026, 12:35 PM UTC

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

  6. resolved Mar 25, 2026, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 12, 2026

Background jobs queue got stuck for some time

Detected by Pingoru
Mar 12, 2026, 04:39 PM UTC
Resolved
Mar 12, 2026, 04:47 PM UTC
Duration
7m
Affected: WebhooksZapierMonitors ( Third-party services )SlackEmailsDatadogPagerDutyMicrosoft TeamsGoogle ChatDiscord
Timeline · 3 updates
  1. identified Mar 12, 2026, 04:39 PM UTC

    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.

  2. monitoring Mar 12, 2026, 04:43 PM UTC

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

  3. resolved Mar 12, 2026, 04:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 5, 2025

Website is currently unavailable

Detected by Pingoru
Dec 05, 2025, 09:03 AM UTC
Resolved
Dec 05, 2025, 09:23 AM UTC
Duration
20m
Affected: Website
Timeline · 4 updates
  1. investigating Dec 05, 2025, 09:03 AM UTC

    We are currently investigating this issue.

  2. identified Dec 05, 2025, 09:13 AM UTC

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

  3. monitoring Dec 05, 2025, 09:15 AM UTC

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

  4. resolved Dec 05, 2025, 09:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

Issues accessing IsDown website.

Detected by Pingoru
Nov 18, 2025, 11:56 AM UTC
Resolved
Nov 18, 2025, 03:56 PM UTC
Duration
3h 59m
Affected: WebsiteMonitors ( Third-party services )Monitors ( Websites )
Timeline · 4 updates
  1. investigating Nov 18, 2025, 11:56 AM UTC

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

  2. investigating Nov 18, 2025, 12:06 PM UTC

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

  3. monitoring Nov 18, 2025, 02:49 PM UTC

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

  4. resolved Nov 18, 2025, 03:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Issues getting the official outages from Azure source

Detected by Pingoru
Oct 29, 2025, 04:39 PM UTC
Resolved
Oct 29, 2025, 05:14 PM UTC
Duration
35m
Affected: Monitors ( Third-party services )
Timeline · 3 updates
  1. investigating Oct 29, 2025, 04:39 PM UTC

    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.

  2. identified Oct 29, 2025, 05:12 PM UTC

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

  3. resolved Oct 29, 2025, 05:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Issues with status page provider

Detected by Pingoru
Oct 20, 2025, 09:47 AM UTC
Resolved
Oct 20, 2025, 10:04 AM UTC
Duration
16m
Affected: Monitors ( Third-party services )
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 09:47 AM UTC

    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.

  2. resolved Oct 20, 2025, 10:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 31, 2025

Problem with custom monitors relying only on probes located in Asia

Detected by Pingoru
Aug 31, 2025, 11:26 PM UTC
Resolved
Aug 31, 2025, 11:39 PM UTC
Duration
12m
Affected: Monitors ( Websites )
Timeline · 3 updates
  1. identified Aug 31, 2025, 11:26 PM UTC

    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.

  2. monitoring Aug 31, 2025, 11:34 PM UTC

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

  3. resolved Aug 31, 2025, 11:39 PM UTC

    This incident has been resolved.

Read the full incident report →