Fastly Status

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

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.

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 Lima (LIM) Point of Presence (POP). 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.

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.

Traffic in Hong Kong (HKG) has been temporarily rerouted. All other locations and services are unaffected.

This scheduled maintenance has been completed.

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.

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.

This scheduled maintenance has been completed.

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.

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 scheduled maintenance has been completed.

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.

The scheduled maintenance has been completed.