Fastly will be adding capacity at our Sydney (WSI) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 03 November 2025 at 17: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.
We're investigating possible performance impact affecting the Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) data center.
All other locations and services are unaffected.
Our engineers believe they have identified contributing factor causing the issue impacting the Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) 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 Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ)
POPs
has been mitigated.
Engineering has confirmed that Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Frankfurt (FRA), London (LCY), London (LHR), Milan (LIN), Rome (FCO), Sofia (SOF), Stockholm (BMA), Vienna (VIE), Fujairah (FJR), Chicago (CHI), Detroit (DTW), Minneapolis (MSP), Sao Paulo (GRU), Paris (PAR), Amsterdam (RTM), Madrid (TOJ) POPs has been fully restored. Customers may have experienced elevated latency, errors and timeouts from 16:15 to 19:00 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-11-01 16:54:05 UTC
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 will be adding capacity at our Sydney (WSI) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 31 October 2025 at 16: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.
The scheduled maintenance has been cancelled and will be rescheduled for the 3rd of November 2025 from 17:00 to 21:00 UTC.
To offer feedback on our status page, click
"
Give Feedback
"
We are issuing an urgent advisory regarding an incompatibility between Compute services and the newly released Rust version 1.91.
Action Required
We strongly recommend that you DO NOT upgrade to Rust version 1.91 at this time.
What Happened
We first identified this incompatibility in our testing environment on the 30th of October 2025, and have since confirmed the same Compute crash behavior in our production environment.
Incompatible Version: Rust 1.91
Compatible Version: Rust 1.90 and below (Previous Stable Versions)
Impact: Using Rust 1.91 with Compute may lead to crash behavior, which will impact your traffic on Fastly.
What’s next? What do I have to do?
If you have already upgraded your services to Rust version 1.91, you must immediately downgrade to the previous stable and compatible version, Rust version 1.90, to prevent or resolve any impact to your traffic.
We are actively working on a fix to ensure compatibility with Rust version 1.91 and will provide an update as soon as a fix is available. Thank you for your patience and understanding.
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.
The Fastly status page https://fastlystatus.com is currently unavailable. Our vendor has advised that the issue is related to an ongoing incident with Azure Portal and they are working to fully restore https://fastlystatus.com . As a temporary workaround our vendor has shifted our status page to https://fastly.status.page .
All other Fastly services are unaffected by this event.
As part of Fastly’s global network expansion, we will be adding Dhanbad (QAM) data center to Fastly's Asia-Pacific (APAC) network.
Traffic served by our Dhanbad (QAM) data center will be aggregated into our APAC region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Dhanbad (QAM) . 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.
To offer feedback on our status page, click "Give Feedback"
We are currently investigating performance issues affecting the availability of manage.fastly.com. CDN delivery, stats aggregation, and all other data plane services are unaffected.
Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application 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 the Fastly Application service has been mitigated.
Engineering has confirmed that the Fastly Application service has been fully restored. Customers may have experienced the following issues: 4xx errors, redirect loops or inability to initiate new login sessions
from 13:56
to
14:21 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click " Give Feedback "
Status Post, Created Date/Time: 2025-10-22 14:20:19 UTC
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.
As part of Fastly’s global network expansion, we will be adding Chandigarh (QAL), Kota (KTU) data center to Fastly's Asia-Pacific (APAC) network.
Traffic served by our Chandigarh (QAL), Kota (KTU) data center will be aggregated into our APAC region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Chandigarh (QAL), Kota (KTU). 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.
To offer feedback on our status page, click "Give Feedback"
We are investigating an elevated error rate within our support ticketing systems. Customers may experience failed support case functions when attempting to generate a support case from Support Chat systems. We ask that customers email Support teams at support@fastly.com to ensure no delays.
Our network availability and all other services are unaffected.
Status Post, Created Date/Time: 2025-10-20 08:21:47 UTC
Note: Our Customer Escalation Management team will update the start date and time of this 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.
Our engineers believe they have identified contributing factor causing the issue impacting the Support Ticketing System status page component.
We 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 our Support Ticketing System has been mitigated.
We're investigating possible performance impact affecting the Frankfurt (FRA) data center.
All other locations and services are unaffected.
Our engineers believe they have identified contributing factor causing the issue impacting the Frankfurt (FRA) 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 Frankfurt (FRA) POP has been mitigated.
Engineering has confirmed that Frankfurt (FRA) POP has been fully restored. Customers may have experienced an increase in latency on Time to First Byte (TTFB) metrics from 14:13 to 17:27 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-10-17 14:51:01 UTC
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.