Paris (PAR)

03 February 2025, 01:00 UTC
Platform Europe Paris (PAR)
 
03 February 2025, 01:00 UTC

Fastly will be expanding Paris (PAR) into a Metro POP. End-users may observe connection resets as traffic is migrated onto new hardware.

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin.

Action for Fastly Customers:

  1. Please verify that all origins allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges), as this list is updated periodically. Failure to verify origin access lists will result in origin connection disruption. 
  2. Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).

For more information on Metro POPs: https://developer.fastly.com/learning/concepts/pop/#metro-pops

 
04 February 2025, 01:00 UTC

The scheduled maintenance has been completed.

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

Platform Europe London (LCY) London (LHR) Manchester (MAN) Paris (CDG) Paris (PAR)
 
28 January 2025, 17:15 UTC

We're investigating possible performance impact affecting the data centers within the Europe region.

All other locations and services are unaffected


 
28 January 2025, 19:22 UTC

Our engineers have identified the contributing factor and have applied a fix. Our investigation has confirmed that impact within the Europe region was limited to the London (LCY and LHR), Manchester (MAN) and Paris (CDG and PAR) data centers.

All other locations and services are unaffected.

 
28 January 2025, 19:33 UTC

Engineering has confirmed the impact to Europe data centers has been mitigated.

 
28 January 2025, 21:03 UTC

Engineering has confirmed that our Europe POPs have been fully restored. Customers may have experienced performance degradation from 17: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-01-28 19:18:00 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.


05 September 2024, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Brussels (BRU) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Copenhagen (CPH) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Dublin (DUB) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (FRA) Perth (PER) Atlanta (PDK) Frankfurt (HHN) Hong Kong (HKG) Rio de Janeiro (GIG) Boston (BOS) Kolkata (CCU) Helsinki (HEL) Sydney (SYD) Santiago (SCL) Calgary (YYC) London (LCY) Kuala Lumpur (KUL) Wellington (WLG) Sāo Paulo (CGH) Chicago (CHI) London (LON) Manila (MNL) Sao Paulo (GRU) Mumbai (BOM) London (LHR) New Delhi (DEL) Lisbon (LIS) Osaka (ITM) Madrid (MAD) Seoul (ICN) Manchester (MAN) Marseille (MRS) Singapore (QPG) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Tokyo (HND) Denver (DEN) Palermo (PMO) Tokyo (NRT) Detroit (DTW) Tokyo (TYO) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

Our engineers are continuing to investigate the impact to our Platform delivery services.

 
05 September 2024, 22:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

 
05 September 2024, 23:00 UTC

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

 
05 September 2024, 23:34 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

 
06 September 2024, 00:48 UTC

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 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

Platform Europe Paris (CDG) Paris (PAR)
 
09 August 2024, 19:09 UTC

We are investigating elevated errors to our Paris (PAR), Paris (CDG) Points of Presence (POPs).

 
09 August 2024, 19:27 UTC

Our engineers have identified the contributing factor and are applying a fix to our Paris (PAR), Paris (CDG) POPs.

 
09 August 2024, 19:28 UTC

Engineering has confirmed the impact to Paris (PAR), Paris (CDG) POPs has been mitigated.

 
09 August 2024, 19:29 UTC

Engineering has confirmed that Paris (PAR), Paris (CDG) POPs have been fully restored. Customers may have experienced latency and elevated errors from 18:35 to 19:14 UTC.

This incident is resolved.

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

Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Atlanta (PDK) Frankfurt (HHN) Boston (BOS) Helsinki (HEL) Calgary (YYC) London (LCY) Chicago (CHI) London (LON) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Denver (DEN) Palermo (PMO) Detroit (DTW) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
23 July 2024, 12:48 UTC

At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions. 

Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.

All other products and services are unaffected by this incident.

 
23 July 2024, 14:29 UTC

Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.

Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.

 
23 July 2024, 16:37 UTC

Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions. 

We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.

 
23 July 2024, 23:52 UTC

Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.

This incident is resolved.

Affected customers would 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

28 August 2023, 19:47 UTC
Platform North America Europe Amsterdam (AMS) Frankfurt (FRA) Atlanta (PDK) Helsinki (HEL) London (LCY) London (LHR) Denver (DEN) Paris (PAR) Stockholm (BMA) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Portland (PDX) San Jose (SJC) Toronto (YYZ)
 
28 August 2023, 19:47 UTC

We're currently investigating performance impacts in Europe, North America.

Customers may experience increased errors and latency in the affected regions.

All other locations and services are unaffected.

 
28 August 2023, 20:00 UTC

This issue has been identified and a fix is being implemented. 

 
28 August 2023, 20:05 UTC

After further investigation, Fastly Engineering has narrowed the scope of impact to the following POPs: Amsterdam (AMS), Stockholm (BMA), Denver (DEN), Frankfurt (FRA), London (LCY), Newark (EWR), Atlanta (FTY), Helsinki (HEL), Palo Alto (PAO), Paris (PAR), London (LHR), Atlanta (PDK), New York (LGA), Portland (PDX), San Jose (SJC), Los Angeles (LGB), Montreal (YUL), Toronto (YYZ). 

Customers may continue to experience latency and errors in these POPs. 

All other locations and services are unaffected.

 
28 August 2023, 21:07 UTC

A fix has been implemented and we are monitoring the results.

 
28 August 2023, 21:35 UTC

This incident has been resolved.

29 June 2023, 18:46 UTC
Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Atlanta (PDK) Frankfurt (HHN) Boston (BOS) Helsinki (HEL) Calgary (YYC) London (LCY) Chicago (CHI) London (LON) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Denver (DEN) Palermo (PMO) Detroit (DTW) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
29 June 2023, 18:46 UTC

We're currently investigating performance impacts in Europe, North America.

All other locations and services are unaffected.

 
29 June 2023, 19:56 UTC

This issue has been identified and a fix is being implemented. 

 
29 June 2023, 21:54 UTC

A fix has been implemented and we are monitoring the results.

 
29 June 2023, 23:54 UTC

This incident has been resolved.

01 March 2023, 00:00 UTC
Platform Europe Paris (PAR)
 
01 March 2023, 00:00 UTC

As part of Fastly’s global network expansion, we will be adding Paris (PAR) data center to Fastly's Europe network. 

Traffic served by our Paris (PAR) data center will be aggregated into our Europe region for billing and stats purposes. We expect that some traffic currently served by our data centers in neighboring regions will shift to Paris (PAR). As such, some customers may see a change in their bills.

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

 
01 March 2023, 02:05 UTC

The scheduled maintenance has been completed.

19 January 2023, 23:05 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Brussels (BRU) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Copenhagen (CPH) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Dublin (DUB) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (FRA) Perth (PER) Atlanta (PDK) Frankfurt (HHN) Hong Kong (HKG) Rio de Janeiro (GIG) Boston (BOS) Kolkata (CCU) Helsinki (HEL) Sydney (SYD) Santiago (SCL) Calgary (YYC) London (LCY) Kuala Lumpur (KUL) Wellington (WLG) Sāo Paulo (CGH) Chicago (CHI) London (LON) Manila (MNL) Sao Paulo (GRU) Mumbai (BOM) London (LHR) New Delhi (DEL) Lisbon (LIS) Osaka (ITM) Madrid (MAD) Seoul (ICN) Manchester (MAN) Marseille (MRS) Singapore (QPG) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Tokyo (HND) Denver (DEN) Palermo (PMO) Tokyo (NRT) Detroit (DTW) Tokyo (TYO) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
19 January 2023, 23:05 UTC

We're currently investigating potential impact to performance with our CDN services.

 
19 January 2023, 23:06 UTC

A fix has been implemented and we are monitoring the results.

 
19 January 2023, 23:48 UTC
On the 19th of January at 23:00 UTC a configuration change was deployed which impacted performance to global CDN delivery. Fastly Engineering reverted the change resulting in immediate recovery at 23:06 UTC. Fastly's Customer Incident Response team is currently preparing a Fastly Service Advisory of today's incident, and will be made available to Fastly Customers.
 
20 January 2023, 00:48 UTC

This incident has been resolved.