Fastly

The third party provider issue affecting Support Ticketing System services has been fully resolved.

All Fastly Customer Support services and CRM systems have been restored and are operating normally. Ticket processing and standard communication channels are fully functional.

We apologize for the inconvenience and appreciate your patience during this interruption to our support channels.

Resolved on 18 June 2026 at 19:53 UTC

We have an update regarding the ongoing Informational affecting Support Ticketing System.

Our provider has reported that a contributing factor has been identified and they are working on a fix.

As a reminder, Fastly's core edge network and security services remain unaffected. Please continue to email [email protected] for any assistance while our standard support and CRM channels remain impacted.

Updated on 18 June 2026 at 18:49 UTC

Our engineers have been informed that our Customer Relationship Management (CRM) provider is currently experiencing an incident. As a result, you may experience slightly delayed responses from our Support team while we implement an internal workaround and monitor this provider's incident updates.

All other Fastly services remain fully operational. Our network and security products continue to deliver without disruption.

We will provide an update if the situation changes.

As part of Fastly’s global network expansion, we will be adding Vancouver (YVR) data center to Fastly's [insert region name] network. 

Traffic served by our  Vancouver (YVR)  data center will be aggregated into our [insert region name ]  region for billing and stats purposes.

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

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

Fastly will be adding capacity at our Vancouver (YVR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 June 2026 at 07:30 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.

Fastly will be adding capacity at our Toronto (YYZ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 June 2026 at 02: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.

Engineering has confirmed that our Lima (LIM) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 17:05 to 17:51 UTC.

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.

…

Engineering has confirmed that our Bogota (BOG) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 17:05 to 17:51 UTC.

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.

Engineering has confirmed the impact to our Bogota (BOG) POP has been mitigated.

Engineering has confirmed the impact to our Lima (LIM) POP has been mitigated.

Our engineers believe they have identified contributing factor causing the issue impacting the Bogota (BOG) 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.

Our engineers believe they have identified contributing factor causing the issue impacting the Lima (LIM) 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.

We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP). 

All other products and services are unaffected by this incident.

We are investigating elevated errors to our Lima (LIM) Point of Presence (POP). 

All other products and services are unaffected by this incident.

The scheduled maintenance has been completed.

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

Our estimated duration is 8h. 

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.

This event has been resolved.

Traffic in Hong Kong (HKG) has been temporarily rerouted.

All other locations and services are unaffected.

This event has been resolved.

Our Engineers have deployed standard mitigations for this impact and continue to monitor our Hong Kong (HKG) performance trends. We will provide an update once the HKG POP has been fully restored. Customers may continue to experience elevated or intermittent errors as the POP recovers.

This event has been resolved.

Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center.

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

This incident has been resolved.

Traffic in Howrah (QAC) has been temporarily rerouted.

All other locations and services are unaffected.

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 …

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.

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.

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.

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.

This incident has been resolved.

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.

This event has been resolved.

Traffic in Houston (IAH) has been temporarily rerouted.

All other locations and services are unaffected.

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.

This event has been resolved.

Traffic in Fortaleza (FOR) has been temporarily rerouted.

All other locations and services are unaffected.

The scheduled maintenance has been completed.

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.

This event has been resolved.

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

All other products and services are unaffected by this incident.

The scheduled maintenance has been completed.

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. 

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.

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.

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 …

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

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.

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

All other services are unaffected.

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.

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

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. …

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

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.

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.