fastly rss feed

Data Center Capacity Expansion for Hong Kong (HKG)

Tue, 27 Oct 2026 17:00:00 +0000

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.

Content Delivery (CDN) with Possible Impact

Mon, 26 Oct 2026 19:13:00 +0000

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 mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

Status Post, Created Date/Time: 2026-10-26 18:28:01 UTC

Content Delivery (CDN) with Possible Impact

Mon, 26 Oct 2026 19:05:00 +0000

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.

Content Delivery (CDN) with Possible Impact

Mon, 26 Oct 2026 18:51:00 +0000

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.

Content Delivery (CDN) with Possible Impact

Mon, 26 Oct 2026 16:36:00 +0000

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.

New York (TSS) Maintenance

Fri, 23 Oct 2026 10:00:00 +0000

The scheduled maintenance has been completed.

New York (TSS) Maintenance

Fri, 23 Oct 2026 04:00:00 +0000

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.

Domainr: Some Top-level Domains (TLDs) may return an 'unknown' status

Fri, 23 Oct 2026 02:20:00 +0000

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.

What happened?

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 none are available, the API returns an "unknown" or “non-authoritative” status.

The API continues to operate normally and returns successful (200) responses. Domain status data for affected TLDs may be less accurate or incomplete.

What’s next? What do I have to do?

There is no workaround, and no action is required on your part. Our Engineering team has already reached out to affected registries to partner with them on supporting and installing compatible certificates. Resolution depends on both this partnership and the completion of necessary system updates by the affected registries. Fastly Support is available to answer questions you may have and provide updates if available.

We sincerely apologize for not providing earlier notice. We will update this status page as we receive more information.

Customers with any other questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.

Retrospective: Impacted Performance in Mumbai (BOM)

Thu, 22 Oct 2026 11:30:00 +0000

This event has been resolved.

Retrospective: Impacted Performance in Mumbai (BOM)

Thu, 22 Oct 2026 07:00:00 +0000

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.

Third-Party Vulnerability Disclosure – php2shell (CVE-2026-109618 & CVE-2026-109619)

Wed, 21 Oct 2026 19:26:00 +0000

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.

What happened?

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. To help protect customer environments, Fastly’s Security Research team, in collaboration with OpenAI and community partners, has developed a Virtual Patch for CVE-2026-109618 and CVE-2026-109619. To learn more about this vulnerability and our proactive protections, please read the blog posts linked in the reference section below.

What you can do

We strongly advise taking the following recommended actions:

Apply Virtual Patching: Fastly Next-Gen WAF customers are strongly encouraged to apply the Virtual Patch for CVE-2026-109618 and CVE-2026-109619 across all vulnerable Edge and on-prem services. Opting in ensures you automatically receive updates as the rule is refined.
Audit Application Servers: Identify all application servers running mod_php or php-fpm and treat all PHP applications as potentially vulnerable.
Patch PHP Upstream: Apply official upstream patches. Patches are available in PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 . For PHP 7.4, 8.0, and 8.1, or older versions, verify available patches with your Linux/package distributor.

Fastly is actively monitoring for exploitation and new variants. Please stay aware of any further updates as this situation develops.

Customers with any questions, requiring emergency WAF onboarding, or needing support may engage with our Support team through support@fastly.com or by contacting your designated account management team members.

Reference:

Retrospective: Impacted Performance in Auckland (AKL)

Wed, 21 Oct 2026 12:20:00 +0000

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.

Retrospective: Impacted Performance in Auckland (AKL)

Wed, 21 Oct 2026 10:20:00 +0000

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.

Amsterdam (RTM) Rerouted Traffic

Wed, 21 Oct 2026 00:07:00 +0000

This incident has been resolved.

Amsterdam (RTM) Rerouted Traffic

Tue, 20 Oct 2026 22:28:00 +0000

Traffic in Amsterdam (RTM) has been temporarily rerouted.

All other locations and services are unaffected.

Sambalpur (QAK), Bhopal (QBL) Maintenance

Tue, 20 Oct 2026 21:00:00 +0000

The scheduled maintenance has been completed.

Sambalpur (QAK), Bhopal (QBL) Maintenance

Tue, 20 Oct 2026 19:20:00 +0000

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.

Retrospective: Impacted Performance in Curitiba (CWB)

Tue, 20 Oct 2026 14:04:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in Curitiba (CWB)

Tue, 20 Oct 2026 13:33:00 +0000

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.

[Action Required] Compute services: Shielding migration from Milan (MXP) to Milan (BGY)

Tue, 20 Oct 2026 01:18:00 +0000

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.

What’s changing?

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 location to our Milan (BGY) POP.

During this migration period, Compute services that reference mxp-milan-it will be redirected to bgy-milan-it. After the migration period ends, mxp-milan-it will no longer be a valid shield location, and Compute services that still reference it will get an error when creating the shield. How your service behaves after that depends on how your code handles that error.

What’s next? What do I have to do?

Compute services

If your Compute service uses mxp-milan-it as a shield location, update it to bgy-milan-it before November 2, 2026. We recommend making this change as soon as possible.

Find every place your service sets mxp-milan-it as a shield location, including shield names in your code and any values your code loads from a config store.
Replace mxp-milan-it with bgy-milan-it.
If you changed your code, build and deploy a new version of your service. If the shield name comes from a config store, update the stored value.
If you manage your service with Terraform or other automation, update the shield name there too, so a later deployment doesn’t restore mxp-milan-it.

For details on Compute services, see our Shielding documentation.

Varnish Configuration Language (VCL) services

If your VCL service uses standard shielding configuration, no action is required. Fastly will redirect your shield traffic to Milan (BGY) automatically.

If your custom VCL or VCL snippets reference mxp-milan-it or the MXP POP in your own logic, update those references to bgy-milan-it before November 2, 2026.

You can also switch your shield location to “bgy-milan-it” yourself in the Fastly control panel. See our Shielding documentation.

When you switch to bgy-milan-it, your origin servers may see a temporary increase in requests while the cache fills in Milan (BGY).

If you have any questions, please contact our Support team through https://support.fastly.com or your account team.

Shielding Migration: Milan (MXP) to Milan (BGY)

Tue, 20 Oct 2026 01:17:00 +0000

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.

Data Center Capacity Expansion for Toronto (YYZ)

Fri, 16 Oct 2026 18:00:00 +0000

This scheduled maintenance has been completed.

Data Center Capacity Expansion for Toronto (YYZ)

Fri, 16 Oct 2026 12:25:00 +0000

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

Delhi (QAG) Rerouted Traffic

Thu, 15 Oct 2026 21:41:00 +0000

This incident has been resolved.

Data Center Capacity Expansion for Toronto (YYZ)

Thu, 15 Oct 2026 04:00:00 +0000

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.

Our estimated duration is 1d.

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 .

Elevated Errors for Singapore (QPG)

Tue, 13 Oct 2026 04:26:00 +0000

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.

Status Post, Created Date/Time: 2026-10-13 03:46:16 UTC

Elevated Errors for Singapore (QPG)

Tue, 13 Oct 2026 04:06:00 +0000

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

Elevated Errors for Singapore (QPG)

Tue, 13 Oct 2026 04:05:00 +0000

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.

Elevated Errors for Singapore (QPG)

Tue, 13 Oct 2026 02:50:00 +0000

We are investigating elevated errors to our Singapore (QPG) Point of Presence (POP).

All other products and services are unaffected by this incident.

Retrospective: Impacted Performance in Cape Town (CPT)

Sat, 10 Oct 2026 03:57:00 +0000

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.

Retrospective: Impacted Performance in Cape Town (CPT)

Sat, 10 Oct 2026 03:12:00 +0000

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.

Sambalpur (QAK) Rerouted Traffic

Fri, 09 Oct 2026 23:30:00 +0000

This event has been resolved.

Shielding Migration: Milan (MXP) to Milan (BGY)

Thu, 08 Oct 2026 00:10:00 +0000

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/

What’s changing?

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.

What’s next? What do I have to do?

No action is required. You may update your service configuration to select the new shield location (bgy-milan-it) if you do not want Fastly to automatically transition your shielded content. If you elect to change your shield selection, your origin servers may experience a temporary increase in request volume while the cache re-establishes in BGY.

If you have any questions or concerns, please contact our Support team through https://support.fastly.com or your account team.

Sambalpur (QAK) Rerouted Traffic

Wed, 07 Oct 2026 22:08:00 +0000

Traffic in Sambalpur (QAK) has been temporarily rerouted.

All other locations and services are unaffected.

Delhi (QAG) Rerouted Traffic

Wed, 07 Oct 2026 22:05:00 +0000

Traffic in Delhi (QAG) has been temporarily rerouted.

All other locations and services are unaffected.

Elevated Errors for API & Configuration Management

Tue, 06 Oct 2026 00:47:00 +0000

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.

Status Post, Created Date/Time: 2026-10-06 00:37:30 UTC

Elevated Errors for API & Configuration Management

Tue, 06 Oct 2026 00:44:00 +0000

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.

Elevated Errors for API & Configuration Management

Tue, 06 Oct 2026 00:42:00 +0000

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.

Elevated Errors for API & Configuration Management

Tue, 06 Oct 2026 00:12:00 +0000

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

All other products and services are unaffected by this incident.

Elevated Errors for Object Storage

Thu, 01 Oct 2026 14:17:00 +0000

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.

Status Post, Created Date/Time: 2026-10-01 10:01:48 UTC

Elevated Errors for Object Storage

Thu, 01 Oct 2026 13:45:00 +0000

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.

Elevated Errors for Object Storage

Thu, 01 Oct 2026 07:55:00 +0000

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.

Elevated Errors for Object Storage

Wed, 30 Sep 2026 23:00:00 +0000

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.

Data Center Capacity Expansion for Miami (MIA)

Wed, 30 Sep 2026 10:00:00 +0000

This scheduled maintenance has been completed.

Data Center Capacity Expansion for Miami (MIA)

Wed, 30 Sep 2026 06:00:00 +0000

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.