Quad9 Outage History

Quad9 is up right now

Quad9 had 15 outages in the last 2 years totaling 1380h 3m of downtime — averaging 0.6 incidents per month.

There were 15 Quad9 outages since December 10, 2025 totaling 1380h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://uptime.quad9.net

Minor September 23, 2026

Service degradation in Asia

Detected by Pingoru
Sep 23, 2026, 11:04 AM UTC
Resolved
Sep 23, 2026, 11:04 AM UTC
Duration
—
Affected: Current status by service (quad9.net)Current status by service (quad9.net)
Timeline · 1 update
  1. investigating Sep 23, 2026, 11:04 AM UTC

    The NTT GIN backbone is currently operating with reduced network capacity in Asia due to multiple concurrent subsea cable outages. The most significant impact is to traffic transiting Singapore, Hong Kong and Taiwan. As traffic is rerouted across available network paths, customers may experience intermittent packet loss and increased latency. On September 21, Typhoon Dujuan impacted Japan, resulting in an additional loss of network capacity. Restoration efforts are currently delayed due to flooding and the risk of landslides in affected areas.

Read the full incident report →

Major June 29, 2026

Some services are down

Detected by Pingoru
Jun 29, 2026, 10:20 AM UTC
Resolved
Jun 29, 2026, 10:20 AM UTC
Duration
—
Affected: Current status by service (quad9.net)Current status by service (quad9.net)
Timeline · 1 update
  1. resolved Jun 29, 2026, 10:20 AM UTC

    Quad9.net (our main website) has experienced a short outage. We are back online now.

Read the full incident report →

Major May 8, 2026

quad9.net is down

Detected by Pingoru
May 08, 2026, 04:11 PM UTC
Resolved
May 08, 2026, 04:35 PM UTC
Duration
23m
Affected: Current status by service (quad9.net)Current status by service (quad9.net)
Timeline · 3 updates
  1. investigating May 08, 2026, 04:11 PM UTC

    quad9.net went down.

  2. resolved May 08, 2026, 04:35 PM UTC

    quad9.net recovered. UPDATE: Nameserver infrastructure used by the quad9.net zone was experiencing intermittent failures. We immediately worked with our relevant technology partner to mitigate the issue. This outage affected Quad9's website and services that use the quad9.net domain name. Services that are hosted on our anycast IP addresses, like 9.9.9.9 and 9.9.9.10, were not affected. We appreciate your patience while we addressed the underlying issue.

  3. resolved May 08, 2026, 04:35 PM UTC

    quad9.net recovered.

Read the full incident report →

Minor May 5, 2026

DE ccTLD Issue Identified

Detected by Pingoru
May 05, 2026, 09:02 PM UTC
Resolved
May 05, 2026, 09:02 PM UTC
Duration
—
Affected: Current status by service (quad9.net)Current status by service (quad9.net)
Timeline · 2 updates
  1. investigating May 05, 2026, 09:02 PM UTC

    We are monitoring a DNSSEC-related issue with DE ccTLD. The issue is not specific to Quad9. We will update once more information becomes available.

  2. resolved May 05, 2026, 09:02 PM UTC

    UPDATE: The issue appears to be resolved. Accordingly, we have removed the NTAs. We will continue to monitor and update if anything changes. _________ We are monitoring a DNSSEC-related issue with DE ccTLD. The issue is not specific to Quad9. UPDATE: As a result of the issue, we have decided to temporarily implement Negative Trust Anchors. You can view our NTA policy here: https://quad9.net/service/negative-trust-anchors/ We will continue to update as more information becomes available.

Read the full incident report →

Minor January 8, 2026

Service degradation in Mars (southern hemisphere)

Detected by Pingoru
Jan 08, 2026, 01:08 PM UTC
Resolved
Jan 08, 2026, 01:08 PM UTC
Duration
—
Affected: Current status by service (quad9.net)Current status by service (quad9.net)
Timeline · 1 update
  1. resolved Jan 08, 2026, 01:08 PM UTC

    We were informed by our users on Mars that they have difficulty accessing our services on that planet. Our engineering team is currently investigating the situation and impact.

Read the full incident report →