Fastly Outage History

Fastly is up right now

Fastly had 47 outages in the last 2 years totaling 2044h 3m of downtime — averaging 1.9 incidents per month.

There were 47 Fastly outages since March 31, 2026 totaling 2044h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.fastlystatus.com

Notice April 24, 2026

Dhanbad (QAM), Raipur (RPR) Rerouted Traffic

Detected by Pingoru
Apr 24, 2026, 01:23 PM UTC
Resolved
Apr 24, 2026, 04:55 PM UTC
Duration
3h 32m
Affected: AsiaDhanbad (QAM)Raipur (RPR)PlatformAsia
Timeline · 2 updates
  1. investigating Apr 24, 2026, 01:23 PM UTC

    Traffic in Dhanbad (QAM), Raipur (RPR) has been temporarily rerouted. All other locations and services are unaffected.

  2. resolved Apr 24, 2026, 04:55 PM UTC

    This event has been resolved.

Read the full incident report →

Notice April 23, 2026

Retrospective: Impacted Performance in Tokyo (NRT)

Detected by Pingoru
Apr 23, 2026, 10:22 PM UTC
Resolved
Apr 23, 2026, 10:32 PM UTC
Duration
10m
Affected: AsiaTokyo (NRT)PlatformAsia
Timeline · 2 updates
  1. investigating Apr 23, 2026, 10:22 PM UTC

    Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

  2. resolved Apr 23, 2026, 10:32 PM UTC

    This event has been resolved.

Read the full incident report →

Major April 23, 2026

Elevated Errors for Dashboard Data

Detected by Pingoru
Apr 23, 2026, 05:47 PM UTC
Resolved
Apr 23, 2026, 07:07 PM UTC
Duration
1h 20m
Affected: Security Console & APIDashboard Data
Timeline · 4 updates
  1. investigating Apr 23, 2026, 05:47 PM UTC

    We are investigating elevated errors to Dashboard Data in our Next Gen-WAF (NGWAF) Dashboard. All other products and services are unaffected by this incident.

  2. investigating Apr 23, 2026, 06:59 PM UTC

    Our engineers believe they have identified contributing factor causing the issue impacting Dashboard Data for our NGWAF Dashboard. We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery. All other products and services are unaffected by this incident.

  3. monitoring Apr 23, 2026, 07:03 PM UTC

    Engineering has confirmed the impact to Dashboard Data for our NGWAF Dashboard has been mitigated.

  4. resolved Apr 23, 2026, 07:07 PM UTC

    Engineering has confirmed that Dashboard Data for our NGWAF Dashboard has been fully restored. From 17:47 to 18:57 UTC, customers may have experienced elevated 5xx errors, degraded performance, blank graphs or the inability to perform searches. Additionally, attempts to view queries from various sites may have failed returning an "Invalid search query" error message. This incident is resolved. Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team. Status Post, Created Date/Time: 2026-04-23 18:37:49 UTC

Read the full incident report →

Notice April 22, 2026

Retrospective: Impacted Performance in Varanasi (VNS)

Detected by Pingoru
Apr 22, 2026, 06:31 PM UTC
Resolved
Apr 22, 2026, 08:51 PM UTC
Duration
2h 20m
Affected: AsiaVaranasi (VNS)PlatformAsia
Timeline · 2 updates
  1. investigating Apr 22, 2026, 06:31 PM UTC

    Fastly Engineers detected a performance impacting event affecting the Varanasi (VNS) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

  2. resolved Apr 22, 2026, 08:51 PM UTC

    During this incident, customers may have experienced elevated errors from 18:34 to 20:51 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

Read the full incident report →