Tokyo (NRT)
Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 March 2026 at 16: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.
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
Our engineers are conducting scheduled maintenance to decommission the TYO (Tokyo) POP. This update will help to consolidate our network footprint in the Tokyo region. To learn more about shielding concepts, please read:https://docs.fastly.com/en/guides/shielding.
What’s Changing?
We are decommissioning the TYO POP to consolidate our presence in the region. The new location name for origin shielding has changed from tyo-tokyo-jp to nrt-tokyo-jp.
What’s next? What do I have to do?
Customers who have met the condition of currently utilizing TYO for their Origin Shield should perform Shielding Migration by March 26th, 2026 in order to avoid potential shielding failures or fallback to unshielded traffic.
Customers may experience a temporary increase in traffic to their origin servers as the cache warms in the new NRT location during the transition.
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 scheduled maintenance has been completed.
We're investigating possible performance impact affecting the Amsterdam (AMS), Milan (MXP), Sofia (SOF), Fujairah (FJR), Osaka (ITM), Singapore (QPG), Tokyo (NRT), Tokyo (TYO), Los Angeles (BUR), Paris (PAR), Singapore (SIN), Amsterdam (RTM) data center.
All other locations and services are unaffected.
Our engineers are continuing to investigate confirmed periods of increased latency and elevated errors to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs.
Our engineers believe they have identified contributing factor causing the issue impacting the Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) 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.
Engineering has confirmed the impact to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs has been mitigated and services are fully restored.
Engineering has confirmed that all POPs have been fully restored. Customers may have experienced elevated errors from 13:35 UTC to 14:15 UTC, a duration of 40 minutes on the 11th of December 2025. 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-12-11 14:34:14 UTC
Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT) POP between 14:00 to 16:00 UTC and 18:00 to 20:15 UTC. During this time customers may have experienced elevated errors and/or latency.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 26 March 2025 at 17:00 UTC.
Our estimated duration is 7h.
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 (support@fastly.com).
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 March 2025 at 15:00 UTC.
Our estimated duration is 9h.
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 (support@fastly.com).
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
We are investigating elevated errors to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute Services and the Fastly Application.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute Services.
All other locations and services are unaffected.
Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute services.
All other locations and services are unaffected.
Engineering has deployed a fix and have confirmed a gradual recovery to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs and Fastly Application service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
After further investigation, Engineering observed impact to our Tokyo (NRT), Tokyo (TYO), and Osaka (ITM) POPs.
Engineering has confirmed that Hyderabad (HYD), Manila (MNL), Osaka (ITM), Tokyo (NRT), Tokyo (TYO), Bogota (BOG), Fastly Application, Johannesburg (JNB), Singapore (SIN) POPs and service have been fully restored. Compute customers may have experienced errors for requests that utilized geolocation as well as login issues with the Fastly Application from the 28th of January at 04:21 to 18:30 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than set forth above.
As the fix was deployed Engineering made additional adjustments to address impact observed to our Tokyo (NRT), Tokyo (TYO), and Osaka (ITM) POPs. Customer during this time may have experienced an increase in error rates from the 28th of January at 23:00 to the 29th of January 05:00 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than set forth above.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-01-28 09:30:53 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 Engineers detected a performance impacting event affecting the Tokyo (NRT) Point of Presence (POP) for Compute services.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 01 October 2024 at 19:00 UTC.
Our estimated duration is 2 days and 4 hours.
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 (support@fastly.com).
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 25 September 2024 at 19:00 UTC.
Our estimated duration is 2d 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 postponed and a subsequent status post will be provided after our engineers have selected the new maintenance duration.
To offer feedback on our status page, click "Give Feedback"