fastly rss feed

Howrah (QAC) Rerouted Traffic

Sat, 06 Jun 2026 23:56:00 +0000

This incident has been resolved.

Howrah (QAC) Rerouted Traffic

Sat, 06 Jun 2026 22:00:00 +0000

Traffic in Howrah (QAC) has been temporarily rerouted.

All other locations and services are unaffected.

Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR)

Sat, 06 Jun 2026 02:25:00 +0000

Engineering has confirmed that our our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) POPs have been fully restored.

Customers may have experienced increased latency from 00:50 to 01:50 UTC at our DFW, DEN, MSP, and EWR POPs and from 00:50 to 02:13 UTC at our PDK and MIA POPs.

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-06-06 01:01:14 UTC

Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR)

Sat, 06 Jun 2026 02:14:00 +0000

Engineering has confirmed the impact to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs) has been mitigated.

Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR)

Sat, 06 Jun 2026 01:53:00 +0000

The fix has been successfully deployed, and we have observed recovery to only our DFW, DEN, MSP, and EWR POPs. Error rates and latency have returned to nominal levels and we are monitoring stability at these locations.

Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our MIA and PDK POPs specifically.

All other locations and services are unaffected.

Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR)

Sat, 06 Jun 2026 01:06:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting the our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) status page components .

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.

Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR)

Sat, 06 Jun 2026 00:50:00 +0000

We are investigating elevated errors to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Retrospective: Impacted Performance in Singapore (SIN)

Fri, 05 Jun 2026 12:52:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in Singapore (SIN)

Fri, 05 Jun 2026 12:00:00 +0000

Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Houston (IAH) Rerouted Traffic

Thu, 04 Jun 2026 09:25:00 +0000

This event has been resolved.

Data Center Capacity Expansion for Chicago (CHI)

Thu, 04 Jun 2026 09:00:00 +0000

This scheduled maintenance has been completed.

Houston (IAH) Rerouted Traffic

Thu, 04 Jun 2026 08:00:00 +0000

Traffic in Houston (IAH) has been temporarily rerouted.

All other locations and services are unaffected.

Data Center Capacity Expansion for Chicago (CHI)

Thu, 04 Jun 2026 05:00:00 +0000

Fastly will be adding capacity at our Chicago (CHI) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 June 2026 at 05:00 UTC.

Our estimated duration is 4h.

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com.

Fortaleza (FOR) Rerouted Traffic

Tue, 02 Jun 2026 16:36:00 +0000

This event has been resolved.

Fortaleza (FOR) Rerouted Traffic

Tue, 02 Jun 2026 15:03:00 +0000

Traffic in Fortaleza (FOR) has been temporarily rerouted.

All other locations and services are unaffected.

Dusseldorf (DUS) New Data Center

Fri, 29 May 2026 05:00:00 +0000

The scheduled maintenance has been completed.

Dusseldorf (DUS) New Data Center

Fri, 29 May 2026 00:00:00 +0000

As part of Fastly’s global network expansion, we will be adding Dusseldorf (DUS) data center to Fastly's Europe network.

Traffic served by our Dusseldorf (DUS) data center will be aggregated into our Europe region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Dusseldorf (DUS) . As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

Elevated Errors for Fortaleza (FOR)

Thu, 28 May 2026 02:29:00 +0000

This event has been resolved.

Elevated Errors for Fortaleza (FOR)

Thu, 28 May 2026 01:38:00 +0000

We are investigating elevated errors to our Fortaleza (FOR) Point of Presence (POP).

All other products and services are unaffected by this incident.

Data Center Capacity Expansion for London (LHR)

Tue, 26 May 2026 04:30:00 +0000

The scheduled maintenance has been completed.

Data Center Capacity Expansion for London (LHR)

Tue, 26 May 2026 00:30:00 +0000

Fastly will be adding capacity at our London (LHR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 26 May 2026 at 00:30 UTC.

Our estimated duration is 4h.

Image Optimizer Performance Issues

Fri, 22 May 2026 12:10:00 +0000

This incident has been resolved. Image Optimization services in Europe are fully restored and operating normally.

Customers may have experienced intermittent errors and elevated latency between 06:50 UTC and 10:02 UTC on May 22, 2026.

We apologize for any disruption this may have caused and thank you for your patience.

Status Post, Created Date/Time: 2026-05-22 09:55:16 UTC

Image Optimizer Performance Issues

Fri, 22 May 2026 10:24:00 +0000

Engineering has confirmed the impact to Image Optimization service has been mitigated.

Image Optimizer Performance Issues

Fri, 22 May 2026 10:20:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting the Image Optimization status page component.

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.

Image Optimizer Performance Issues

Fri, 22 May 2026 06:50:00 +0000

We're currently investigating performance issues with our Image Optimization service in Europe.

All other services are unaffected.

Retrospective: Impacted Performance in Ashburn (IAD)

Thu, 21 May 2026 21:35:00 +0000

The issue causing temporary unhealthy cache nodes was resolved, and services were fully restored.

Our engineers confirmed that all cache nodes returned to a healthy state. Customers may have experienced impact between 21:29 UTC and 21:35 UTC (approximately 6 minutes).

All other services and locations were unaffected by this event.

Retrospective: Impacted Performance in Ashburn (IAD)

Thu, 21 May 2026 21:29:00 +0000

Fastly Engineers detected a performance impacting event affecting the Ashburn (IAD) data center.

Elevated Errors for API Services

Wed, 20 May 2026 20:19:00 +0000

Our engineers have confirmed that the Fastly API (api.fastly.com) has been fully restored. Customers may have experienced elevated 503 errors, increased timeouts, or failures on API calls and Terraform builds from approximately 18:35 to 19:37 UTC.

As a side effect of the API degradation, the following areas were also impacted during this period:

Next-Gen WAF (NGWAF) rule and configuration updates may have been delayed in taking effect
Fastly account sign-up may have experienced disruptions
Fastly Support Portal functionality may have been affected

Service has been fully restored. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

This incident is resolved.

Status Post, Created Date/Time: 2026-05-20 19:31:03 UTC

Elevated Errors for API Services

Wed, 20 May 2026 20:18:00 +0000

Engineering has confirmed the impact to API Services has been mitigated.

Elevated Errors for API Services

Wed, 20 May 2026 20:02:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting the API Services status page component .

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.

Elevated Errors for API Services

Wed, 20 May 2026 18:35:00 +0000

We are investigating an issue causing errors and timeouts for customers using the Fastly API (api.fastly.com).

Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour.

All other products and services are unaffected by this incident.

Ambala (QAA) Rerouted Traffic

Sun, 17 May 2026 03:26:00 +0000

Engineering has confirmed that Ambala (QAA) POP has been fully restored. Customers may have experienced elevated intermittent errors or periods of latency while traffic was rerouted from 01:27 to 03:26 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

Status Post, Created Date/Time: 2026-05-17 01:53:50 UTC

Ambala (QAA) Rerouted Traffic

Sun, 17 May 2026 02:59:00 +0000

Update: The responding escalation manager erroneously marked the incorrect status page component in their original post which caused the wrong title to appear within customer support chat and email threads. This was corrected to display the proper component (Ambala (QAA)).

All other components, locations and services were unaffected by this event.

Ambala (QAA) Rerouted Traffic

Sun, 17 May 2026 01:27:00 +0000

Traffic in Ambala (QAA) has been temporarily rerouted.

All other locations and services are unaffected.

Elevated Errors for TLS Provisioning

Wed, 13 May 2026 07:15:00 +0000

Engineering has confirmed that our TLS Provisioning service has been fully restored. Customers may have experienced errors and timeouts when using the TLS provisioning API from 06:06 to 07:12 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

Status Post, Created Date/Time: 2026-05-13 06:55:15 UTC

Elevated Errors for TLS Provisioning

Wed, 13 May 2026 07:12:00 +0000

Engineering has confirmed the impact to TLS Provisioning service has been mitigated.

Elevated Errors for TLS Provisioning

Wed, 13 May 2026 07:01:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting the TLS Provisioning features via API and Web application.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

Elevated Errors for TLS Provisioning

Wed, 13 May 2026 06:06:00 +0000

We are investigating elevated errors to our TLS Provisioning feature.

Retrospective: Impacted Performance in TLS Provisioning

Tue, 12 May 2026 13:59:00 +0000

This event has been resolved.

Retrospective: Impacted Performance in TLS Provisioning

Tue, 12 May 2026 13:49:00 +0000

Fastly Engineers detected a performance impacting event affecting the TLS Provisioning service.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Retrospective: Impacted Performance in TLS Provisioning

Tue, 12 May 2026 02:54:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in TLS Provisioning

Tue, 12 May 2026 02:15:00 +0000

From 12 May 2026, 02:15 UTC to 02:54 UTC, we experienced an issue affecting the availability of our TLS management features.

During this time, customers may have experienced errors and timeouts when using the TLS management API. Customers accessing TLS via manage.fastly.com were also affected.

CDN delivery, stats aggregation, and all other data plane services were unaffected.

The issue has been resolved and all services are operating normally.