fastly rss feed

Retrospective: Impacted Performance in Johannesburg (JNB)

Sat, 18 Apr 2026 19:37:00 +0000

During this incident, customers may have experienced elevated errors from 19:01 to 19:12 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 Johannesburg (JNB)

Sat, 18 Apr 2026 19:24:00 +0000

Fastly Engineers detected a performance impacting event affecting the Johannesburg (JNB) data center.

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

Elevated Errors for Image Optimization

Fri, 17 Apr 2026 21:18:00 +0000

Engineering has confirmed that our Image Optimization service has been fully restored. Customers may have experienced elevated 5xx errors for shield traffic routed to POPs in our west North American region from 19:20 to 21:05 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.

Status Post, Created Date/Time: 2026-04-17 20:16:01 UTC

Elevated Errors for Image Optimization

Fri, 17 Apr 2026 21:09:00 +0000

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

Elevated Errors for Image Optimization

Fri, 17 Apr 2026 20:16:00 +0000

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.

Elevated Errors for Image Optimization

Fri, 17 Apr 2026 19:20:00 +0000

We are investigating elevated errors to our Image Optimization for traffic shielding at Points of Presence (POPs) in our west North American region.

All other products and services are unaffected by this incident.

Retrospective: Impacted Performance for API Services

Fri, 17 Apr 2026 12:55:00 +0000

During this incident, customers may have experienced high API latency, high API service error rates and slow loading or errors when attempting to access manage.fastly.com from 12:40 to 12:55 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 for API Services

Fri, 17 Apr 2026 12:40:00 +0000

Fastly Engineers detected a performance impacting event affecting our API Services.

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

Data Center Capacity Expansion for Fortaleza (FOR)

Fri, 17 Apr 2026 08:00:00 +0000

This scheduled maintenance has been completed.

Data Center Capacity Expansion for Fortaleza (FOR)

Fri, 17 Apr 2026 04:00:00 +0000

Fastly will be adding capacity at our Fortaleza (FOR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 April 2026 at 04: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.

Data Center Capacity Expansion for London (LHR)

Fri, 17 Apr 2026 03:00:00 +0000

The scheduled maintenance has been completed.

Data Center Capacity Expansion for London (LHR)

Thu, 16 Apr 2026 23:00:00 +0000

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 16 April 2026 at 23:00 UTC.

Our estimated duration is 4h.

CDN Global Performance Impact

Thu, 16 Apr 2026 18:29:00 +0000

Engineering has confirmed that our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs have been fully restored.

Customers may have experienced elevated 5xx errors from 17:13 to 17:45 UTC.

This incident is resolved.

Status Post, Created Date/Time: 2026-04-16 18:21:26 UTC

CDN Global Performance Impact

Thu, 16 Apr 2026 18:28:00 +0000

Engineering has confirmed the impact to our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs has been mitigated.

CDN Global Performance Impact

Thu, 16 Apr 2026 18:22:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs.

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.

CDN Global Performance Impact

Thu, 16 Apr 2026 17:13:00 +0000

We are investigating elevated errors to our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Retrospective: Impacted Performance in Hong Kong (HKG)

Wed, 15 Apr 2026 01:12:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in Hong Kong (HKG)

Wed, 15 Apr 2026 00:52:00 +0000

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.

Elevated Errors for Hong Kong (HKG)

Tue, 14 Apr 2026 02:17:00 +0000

Engineering has confirmed that Hong Kong (HKG) POP has been fully restored. Customers may have experienced slow loading and elevated errors from 1:57am to 2:17am UTC.

This incident is resolved.

Status Post, Created Date/Time: 2026-04-14 02:15:25 UTC

Elevated Errors for Hong Kong (HKG)

Tue, 14 Apr 2026 01:57:00 +0000

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

All other products and services remain unaffected by this incident.

Minneapolis (STP) Rerouted Traffic

Sun, 12 Apr 2026 12:00:00 +0000

This event has been resolved.

Minneapolis (STP) Rerouted Traffic

Sun, 12 Apr 2026 09:02:00 +0000

Traffic in Minneapolis (STP) has been temporarily rerouted.

All other locations and services are unaffected.

Houston (IAH) Rerouted Traffic

Fri, 10 Apr 2026 09:00:00 +0000

This event has been resolved.

Houston (IAH) Rerouted Traffic

Fri, 10 Apr 2026 04:30:00 +0000

Traffic in Houston (IAH) has been temporarily rerouted.

All other locations and services are unaffected.

Retrospective: Impacted Performance for API Services

Thu, 09 Apr 2026 11:00:00 +0000

During this incident, customers may have experienced issues with our API services from 10:36 to 11:00 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 for API Services

Thu, 09 Apr 2026 10:36:00 +0000

Fastly Engineers detected a performance impacting event affecting our API Services.

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

Elevated Errors for Port Blair (IXZ)

Thu, 09 Apr 2026 04:53:00 +0000

This event has been resolved.

Elevated Errors for Port Blair (IXZ)

Thu, 09 Apr 2026 02:30:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting the Port Blair (IXZ) 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 Port Blair (IXZ)

Thu, 09 Apr 2026 01:30:00 +0000

We are investigating elevated errors to our Port Blair (IXZ) Point of Presence (POP)

All other products and services are unaffected by this incident.

Hong Kong (HKG) Rerouted Traffic

Thu, 09 Apr 2026 00:30:00 +0000

This event has been resolved.

Hong Kong (HKG) Rerouted Traffic

Wed, 08 Apr 2026 23:00:00 +0000

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

All other locations and services are unaffected.

Retrospective: Impacted Performance in Wellington (WLG)

Wed, 08 Apr 2026 21:54:00 +0000

This event has been resolved.

Retrospective: Impacted Performance in Wellington (WLG)

Wed, 08 Apr 2026 21:38:00 +0000

Fastly Engineers detected a performance impacting event affecting the Wellington (WLG) data center.

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

Retrospective: Impacted Performance in API Services, Image Optimization

Tue, 07 Apr 2026 21:15:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in API Services, Image Optimization

Tue, 07 Apr 2026 20:37:00 +0000

Fastly Engineers detected a performance impacting event affecting the API Services, Image Optimization , Terraform and use of those services via the Fastly app.

Between 20:37 UTC and 21:15 UTC on April 7, 2026, customers attempting to disable Service Level products or enable/disable Image Optimizer via the API may have experienced errors, with affected requests returning 500 responses.

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

Retrospective: Impacted Performance in Johannesburg (JNB)

Tue, 07 Apr 2026 19:10:00 +0000

During this incident, customers may have experienced elevated errors and timeouts from 19:02 to 19:10 UTC (approximately 8 minutes).

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 Johannesburg (JNB)

Tue, 07 Apr 2026 19:02:00 +0000

Fastly Engineers detected a performance impacting event affecting the Johannesburg (JNB) data center.

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

Ghana (ACC) Rerouted Traffic

Fri, 03 Apr 2026 18:24:00 +0000

The start of the rerouted effort is 17:55 UTC. The earlier post contained a time entry error.

All other services are unaffected by this informational update.

Ghana (ACC) Rerouted Traffic

Fri, 03 Apr 2026 17:55:00 +0000

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

Retrospective: Impacted Performance in Columbus (CMH)

Fri, 03 Apr 2026 08:30:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in Columbus (CMH)

Fri, 03 Apr 2026 08:20:00 +0000

Fastly Engineers detected a performance impacting event affecting the Columbus (CMH) data center.

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

Upcoming upgrade to a new Compiler platform

Wed, 01 Apr 2026 16:30:00 +0000

We are proceeding with the migration of our modern compiler platform. This architectural update strengthens the systems that deploy and propagate configuration to the edge, introducing improvements in scalability, observability, and validation to ensure consistent and reliable delivery.

What’s Changing?

On April 6, 2026, at 13:00 UTC, we will begin deploying an upgrade to our Compiler Platform.

To ensure a seamless transition, this upgrade will be rolled out gradually across our platform throughout the following weeks.

Fastly Engineering designed this modern compiler platform architecture for enhanced scalability and resilience. By migrating to this new system, we are delivering on key improvements:

Purpose-built scalability: We improve scalability and reduce capacity constraints inherent in the legacy environment.
Optimized build pipeline: We optimized the build processing pipeline to reduce resource contention and increase the overall volume of work the system can handle.

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

Nothing. All actions taken during this upgrade belong to Fastly and there is no anticipated action or impact for our customers.

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

Siliguri (IXB), Shillong (SHL) New Data Center

Tue, 31 Mar 2026 22:00:00 +0000

The scheduled maintenance has been completed.

Siliguri (IXB), Shillong (SHL) New Data Center

Tue, 31 Mar 2026 18:00:00 +0000

As part of Fastly’s global network expansion, we will be adding Siliguri (IXB), Shillong (SHL) data centers to Fastly's Asia network.

Traffic served by our Siliguri (IXB), Shillong (SHL) data centers will be aggregated into our Asia region for billing and stats purposes.

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

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

Elevated Errors for Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Sat, 28 Mar 2026 01:59:00 +0000

Our engineers have confirmed that our Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), and Los Angeles (LAX) Points of Presence have been fully restored.

Customers may have experienced intermittent periods of increased latency and elevated errors from March 28, 2026 at 00:55 to 01:33 UTC.

This incident is resolved. Affected customers would have experienced impact to varying degrees and to a shorter duration than as set forth above.

Status Post, Created Date/Time: 2026-03-28 01:16:07 UTC

Elevated Errors for Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Sat, 28 Mar 2026 01:54:00 +0000

Engineering has deployed a fix and have confirmed recovery to Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX) POPs. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

All other services were unaffected by this incident.

Elevated Errors for Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Sat, 28 Mar 2026 01:39:00 +0000

Our engineers believe they have identified contributing factor causing the issue impacting the Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX) 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 Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Sat, 28 Mar 2026 00:55:00 +0000

We are investigating elevated errors to multiple Points of Presence: Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Customers may experience intermittent periods of increased latency and elevated errors while we investigate into the contributing factors causing this impact.

Retrospective: Impacted Performance in Chicago (CHI)

Thu, 26 Mar 2026 23:22:00 +0000

During this incident, customers may have experienced elevated errors from 23:09 to 23:22 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 Chicago (CHI)

Thu, 26 Mar 2026 23:09:00 +0000

Fastly Engineers detected a performance impacting event affecting the Chicago (CHI) data center.

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

Hyderabad (QBN) New Data Center

Thu, 26 Mar 2026 22:00:00 +0000

The scheduled maintenance has been completed.

Hyderabad (QBN) New Data Center

Thu, 26 Mar 2026 18:00:00 +0000

As part of Fastly’s global network expansion, we will be adding Hyderabad (QBN) data center to Fastly's Asia network.

Traffic served by our Hyderabad (QBN) data center will be aggregated into our Asia region for billing and stats purposes.

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

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

Retrospective: Impacted Performance in Osaka (ITM)

Wed, 25 Mar 2026 12:02:00 +0000

This incident has been resolved.

Retrospective: Impacted Performance in Osaka (ITM)

Wed, 25 Mar 2026 11:31:00 +0000

Fastly Engineers detected a performance impacting event affecting the Osaka (ITM) data center.

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

Vancouver (YVR) Rerouted Traffic

Wed, 25 Mar 2026 11:10:00 +0000

This event has been resolved.

Vancouver (YVR) Rerouted Traffic

Wed, 25 Mar 2026 08:30:00 +0000

Traffic in Vancouver (YVR) has been temporarily rerouted.

All other locations and services are unaffected.