We are investigating elevated errors with product enablements in our Fastly Application.
All other products and services are unaffected by this incident.
Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application 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.
Engineering has confirmed the impact to Fastly Application service has been mitigated.
Engineering has confirmed that Fastly Application service has been fully restored. Customers may have experienced failures with enablement, disablement, and configuration operations, as well as enablement checks from 17:25 to 18:22 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.
Traffic in London (QQP) has been temporarily rerouted.
All other locations and services are unaffected.
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.
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 support@fastly.com for any assistance while our standard support and CRM channels remain impacted.
Updated on 18 June 2026 at 18:49 UTC
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.
We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP).
All other products and services are unaffected by this incident.
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.
Engineering has confirmed the impact to our Bogota (BOG) POP has been mitigated.
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.
We are investigating elevated errors to our Lima (LIM) Point of Presence (POP).
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.
Engineering has confirmed the impact to our Lima (LIM) POP has been mitigated.
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.
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.
The scheduled maintenance has been completed.
Traffic in Hong Kong (HKG) has been temporarily rerouted.
All other locations and services are unaffected.
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.
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.
