We're investigating elevated errors in our Madrid (MAD) Point of Presence (POP).

All other locations and services are unaffected

Fastly Engineering has observed elevated errors in our Madrid (MAD) Point of Presence (POP).

This has been identified as an issue with a third party service provider and a fix is being implemented. 

All other locations and services are unaffected.

Fastly Engineering has applied our standard acute incident response practices and restored our MAD POP.

Customer services have returned to pre-incident performance levels.

We will continue to monitor the third party service provider issue for recovery. All locations and other services remain unaffected.

This event has been resolved.

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

Status Post, Created Date/Time: 2025-02-05 22:01:42 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.

We are investigating elevated errors to our Web Delivery service within our Madrid (MAD) Point of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers are continuing to investigate elevated errors to our Madrid (MAD), Web Delivery service within our Madrid (MAD) Point of Presence (POP).

Our engineers have identified the contributing factor and are applying a fix to our Web Delivery service within our Madrid (MAD) Point of Presence (POP).

All other locations and services are unaffected.

Our engineers have identified an additional contributing factor and are applying an adjusted mitigation strategy to our Web Delivery service within our Madrid (MAD) Point of Presence (POP).

All other locations and services are unaffected.

Engineering has confirmed that our Web Delivery within our Madrid (POP) has been fully restored. Customers may have experienced timeouts and/or inability to view content that was serviced by impacted IPs from the 3rd of February 2025 at 15:48 to the 10th of February 2025 at 16:43 UTC. 

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

If customers are still experiencing elevated errors within this region please reach out to https://support.fastly.com.

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

Status Post, Created Date/Time: 2025-02-03 18:04:21 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.

We are investigating elevated errors to our Platform delivery services.

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

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

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

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.

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" 

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.

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.

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.

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" 

Fastly will be adding capacity at our Madrid (MAD) Point of Presence (POP). End-users may observe connection resets as traffic is migrated onto new hardware, starting on 15 August 2023 at 02: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. 

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.

The scheduled maintenance has been completed.

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

All other locations and services are unaffected.

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

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

This incident has been resolved.

Fastly will be adding capacity at our Madrid (MAD) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 25 April 2023 at 23:00 UTC.

• Our estimated duration is 4h 

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please be sure to check 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.

We're investigating possible performance impact affecting the Madrid (MAD) data center.

All other locations and services are unaffected

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

This incident has been resolved.

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

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

This incident has been resolved.

Fastly is aware of an expected critical vulnerability the OpenSSL project is expected to disclose in the near future. We are studying the currently available information surrounding this vulnerability and do not currently believe that Fastly is vulnerable. We will continue to monitor as additional information is released and will provide our customers with more information as available.

Fastly has reviewed the initial notification from OpenSSL regarding CVE-2022-3786 and CVE-2022-3602. We have analyzed the versions of OpenSSL in use at Fastly, and verified that we do not use OpenSSL 3.x. Fastly and customer usage of Fastly services are not vulnerable to CVE-2022-3786 or CVE-2022-3602.