Tokyo (NRT)

31 October 2026, 19:19 UTC
Platform Asia Osaka (ITM) Tokyo (NRT)
 
31 October 2026, 19:19 UTC

We are investigating an issue causing increased errors and latency for our content delivery service in the Osaka (ITM) and Tokyo (NRT) Points of Presence (POPs).

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.

 
31 October 2026, 21:20 UTC

Our engineers believe they have identified the contributing factor causing the issue impacting our content delivery service in the ITM and NRT POPs.

We 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.

 
31 October 2026, 22:18 UTC

The fix has been successfully deployed, and we have observed a recovery of our content delivery service in the ITM and NRT POPs.

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.

 
31 October 2026, 22:40 UTC

Our engineers have confirmed that our content delivery service in the ITM and NRT POPs has been fully restored.

Customers may have experienced increased errors and latency from 19:19 to 21:36 UTC. Service has been fully restored.



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-31 20:40:55 UTC    

Platform North America Asia Chicago (CHI) Columbus (CMH) Tokyo (NRT) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) Phoenix (PHX) Toronto (YYZ)
 
23 August 2026, 01:06 UTC

Between 01:06 UTC and 01:51 UTC on August 23, 2026, Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs).

During this time, customers with traffic routed through these locations may have experienced elevated error rates or latency. All other data centers and services were unaffected.

The issue has been resolved and we are monitoring performance closely.

Platform Asia Tokyo (NRT)
 
23 April 2026, 22:22 UTC

Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT) data center.

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

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

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.

 
16 April 2026, 18:22 UTC

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.

 
16 April 2026, 18:28 UTC

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.

 
16 April 2026, 18:29 UTC

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.



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-16 18:21:26 UTC    

Platform Asia Tokyo (NRT)
 
18 March 2026, 16:00 UTC

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.

 
18 March 2026, 20:00 UTC

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

Platform Asia Tokyo (NRT) Tokyo (TYO)
 
10 February 2026, 20:19 UTC

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.
 
26 March 2026, 22:59 UTC

The scheduled maintenance has been completed.


Platform North America Europe Asia South America Africa Amsterdam (AMS) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Buenos Aires (EZE) Johannesburg (JNB) Fujairah (FJR) Fortaleza (FOR) Rio de Janeiro (GIG) Frankfurt (FRA) Kuala Lumpur (KUL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LON) Singapore (SIN) Marseille (MRS) Tokyo (NRT) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Sofia (SOF)
 
11 December 2025, 13:35 UTC

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.

 
11 December 2025, 14:39 UTC

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.

 
11 December 2025, 14:41 UTC

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. 

 
11 December 2025, 15:23 UTC

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.

 
11 December 2025, 15:35 UTC

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 


Platform Asia Tokyo (NRT)
 
29 April 2025, 20:52 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.

Platform Asia Tokyo (NRT)
 
26 March 2025, 17:00 UTC

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).

 
26 March 2025, 23:38 UTC

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

Platform Asia Tokyo (NRT)
 
17 March 2025, 15:00 UTC

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).

 
18 March 2025, 00:00 UTC

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback"