Fastly

Fastly will be adding capacity at our Hong Kong (HKG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 27 October 2026 at 17:00 UTC.

Our estimated duration is 6h. 

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.

Our engineers have identified the contributing factor causing the issue impacting our network services in the Johannesburg (JNB) Point of Presence (POP).

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

Customers in the Cape Town (CPT) POP were temporarily impacted between 14:35 and 14:54 UTC. Services in CPT have since fully recovered.

All other products and services remain unaffected by this incident.

We are investigating an issue causing errors and increased latency for our network services in the Johannesburg (JNB) Point of Presence (POP).

Please note that customers in the Cape Town (CPT)  POP were temporarily impacted by this issue between 14:35 and 14:54 UTC; however, services in CPT have since fully recovered.

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.

Our engineers have confirmed that On-the-Fly Packaging (OTFP) has been fully restored.
Customers may have experienced 503 errors from 16:36 to 18:57 UTC on October 26, 2026. 

This incident is resolved.

Affected customers may have experienced impact to varying degrees and for a shorter duration than stated above

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 …

The fix has been successfully deployed, and we have observed a recovery of On-the-Fly Packaging (OTFP).

Error rates and latency have returned to nominal levels.

Our team will continue to monitor the platform to ensure stability before we resolve this incident.

Our engineers believe they have identified the contributing factor causing the issue impacting On-the-Fly Packaging (OTFP).

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

All other products and services remain unaffected by this incident.

We are investigating an issue causing 503 errors for customers using On-the-Fly Packaging (OTFP).

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.

The scheduled maintenance has been completed.

Fastly will be performing scheduled maintenance on our New York (TSS) data center from 23 October 2026, 04:00 UTC - 23 October 2026, 10:00 UTC.

During this time frame traffic will be redirected to neighboring POPs in the region.

Recently Fastly identified an issue affecting Domainr and Domain Research API. This issue may result in non-authoritative or "unknown" domain statuses for certain top-level domains (TLDs) for our customers. 

Domainr verifies domain status by connecting directly to registries. Following a routine certificate rotation, the new certificate no longer includes the client authentication component that some registries require to accept these connections. This reflects a public certificate authority (CA) change that took place earlier this year.

For the affected TLDs, Domainr can't verify status directly with the registry. It falls back to resellers, DNS, or WHOIS where available. In situations where …

This event has been resolved.

Fastly Engineers detected a performance impacting event affecting the Mumbai (BOM) data center from 07:00 to 11:00 UTC on October 22, 2026.

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

A security disclosure regarding php2shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) was published on October 21, 2026. In addition to implementing certain mitigations, we published a blog post about this disclosure for all customers. The post explains how we responded and shares steps you can take to protect your services. Additionally, we have published a second deep dive blog post to help you navigate and implement your own fixes.

A set of critical vulnerabilities affecting all maintained PHP versions (php2shell) was disclosed, involving how the PHP engine handles fatal errors like memory exhaustion, timeouts, and dropped connections. …

During this incident, customers may have experienced elevated errors from 10:20 to 12:20 UTC.

This incident is resolved.

For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

Fastly Engineers detected a performance impacting event affecting the Auckland (AKL) 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 Amsterdam (RTM) has been temporarily rerouted.

All other locations and services are unaffected.

The scheduled maintenance has been completed.

Fastly will be performing scheduled maintenance on our Bhopal (QBL) and Sambalpur (QAK) data centers from 10 October 2026, 19:20 UTC -  10 October 2026, 21:00 UTC .

During this time frame traffic will be redirected to neighboring POPs in the region.

This incident has been resolved.

Fastly Engineers detected a performance impacting event affecting the Curitiba (CWB) data center.

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

Our previous status post about this migration said no action was required. That was incorrect for Compute services that use mxp-milan-it as a shield location. If you have a Compute service that shields at Milan (MXP), you need to update it by November 2, 2026. Fastly can’t make this change for you because the shield location is set in your service’s code or Compute Config Store. We’re sorry for the confusion.

Fastly is decommissioning the Milan (MXP) POP. Beginning October 26, 2026, and concluding by November 2, 2026, Fastly will gradually redirect shield traffic for the mxp-milan-it shield …

We’ve identified an additional required action for customers using shielding in Compute services. We’ll be sharing a new status post with updated instructions.

Varnish Configuration Language (VCL) services using standard shielding configurations remain unaffected and no action is required.

The scheduled maintenance has been extended to 16 October 2026 at 18:00 UTC. We will provide updates as necessary.

This incident has been resolved.

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 15 October 2026 at 04:00 UTC.

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 Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors from 2:50 to 3:53 UTC.

This incident is resolved.

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

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 …

Engineering has confirmed the impact to Singapore (QPG) POP has been mitigated.

Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (QPG) 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 Singapore (QPG) Point of Presence (POP).

All other products and services are unaffected by this incident.

During this incident, customers may have experienced elevated errors from 03:12 to 03:57 UTC.

This incident is resolved.

For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

Fastly Engineers detected a performance impacting event affecting the Cape Town (CPT) 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.

Our engineers are conducting scheduled maintenance to decommission the Milan (MXP) POP. This update will help to consolidate our network footprint in the Italy region. To learn more about shielding concepts, please read: https://www.fastly.com/documentation/guides/getting-started/hosts/shielding/

Beginning October 26, 2026, and concluding by November 2, 2026, Fastly will gradually redirect shield traffic for the mxp-milan-it shield location to our Milan (BGY) POP. Services that use mxp-milan-it will continue to reference it, and the redirect will happen automatically.

No action is required. You may update your service configuration to select the new shield location …

Traffic in Sambalpur (QAK) has been temporarily rerouted.

All other locations and services are unaffected.

Traffic in Delhi (QAG) has been temporarily rerouted.

All other locations and services are unaffected.

As part of Fastly’s global network expansion, we will be adding a Mexico City (AZP) to Fastly's Mexico City network. 

This facility will initially launch as a limited availability deployment on the 7th of October 2026, meaning not all customer traffic will be routed through this new location during this initial phase.

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 Public IP List | Fastly Documentation.

Customers with any questions or …

Engineering has confirmed that API & Configuration Management has been fully restored. Customers may have experienced elevated errors and latency from 00:12 to 00:35 UTC.

This incident is resolved.

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

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 …

Engineering have confirmed a gradual recovery to API & Configuration Management . We will continue to monitor until we’ve confirmed that customer and end user  experience has been fully restored.

Our engineers believe they have identified contributing factor causing the issue impacting the API & Configuration Management 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 that API & Configuration Management has been fully restored. Customers may have experienced elevated errors and latency from 00:12 to 00:35 UTC.

This incident is resolved.

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

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 …

We are investigating elevated errors and latency to our API & Configuration Management

All other products and services are unaffected by this incident.

Our engineers have confirmed that Object Storage uploads (EU-Central) have been fully restored.

Customers may have experienced upload failures and elevated latency from approximately 23:00 UTC on September 30 to 12:26 UTC on October 1.

Service has been fully restored.

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 …

Engineering has confirmed the impact to Object Storage (EU-Central) has been mitigated.

Our team will continue to monitor the platform to ensure stability before we resolve this incident.

Our engineers believe they have identified the contributing factor causing the issue impacting Fastly Object Storage.

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

All other products and services remain unaffected by this incident.

We are investigating an issue causing intermittent failures when uploading objects to Fastly Object Storage in the EU-Central region.

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.

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