Traffic in Ghana (ACC) has been temporarily rerouted.
All other locations and services are unaffected.
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.
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.
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.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.
The scheduled maintenance has been completed.
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.
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.
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.
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.
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 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.
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.
The scheduled maintenance has been completed.
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.
Traffic in Vancouver (YVR) has been temporarily rerouted.
All other locations and services are unaffected.
We are investigating elevated errors to our API Services
Our engineers believe they have identified contributing factor causing the issue impacting the API Services 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 API Services service has been mitigated.
Engineering has confirmed that API Services service has been fully restored. Customers may have experienced elevated 5xx errors from our API from 06:00 to 06:40 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 the status post was requested by our Acute Incident Response team.
