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.

Our engineers have received reports of inaccurate or incomplete Geolocation Data from our customers. A fix has been identified and is being deployed to restore this service.

This fix is being deployed gradually throughout our fleet at a high priority, but our customers may continue to observe varying degrees of inaccurate or incomplete Geolocation data until this issue is resolved.

We will update and close this status post once the deploy is complete and the service has been confirmed by our engineers as having been fully restored.

Our network delivery and all other services remain unaffected by this issue.

We are investigating elevated errors to our Geolocation Data.

Engineering has confirmed the impact to Geolocation Data has been mitigated.

Our engineers have confirmed that the impact to our Geolocation services has been restored to pre-incident levels. There will be a scheduled deployment to further reduce the risk of future impact, and we will continue to monitor the service with a high priority until this updated configuration has been deployed.

Once our deployment has been confirmed, we will resolve this status post.

Engineering has confirmed that Geolocation Data has been fully restored. Customers may have experienced failing Geolocation lookups in Compute from 11:00 to 20:00 UTC.

This incident is resolved.

As described in our April 7, 2022 deprecation of support notice, a third-party vendor for one of Fastly’s geolocation databases is retiring their legacy geoip database. Fastly engineering team will start performing maintenance as part of the retirement of the legacy geoip.* VCL variables beginning May 9th, 2022 at 16:00 UTC. All Fastly services still using the legacy geolocation variables will be migrated by Fastly to the geolocation database using the client.geo.* variables between May 9th 2022 and May 27th 2022. The two sets of geolocation variables use databases from two different third-party vendors and some variable values differ between the two vendors. Fastly has documented the notable differences between the two sets of variables on our Developer Hub here: https://developer.fastly.com/reference/vcl/variables/geolocation/ Starting May 27th 2022, Fastly will no longer support the legacy geolocation geoip.* VCL variables and all instances of them in Fastly services must be removed by this date. Customers should use the client.geo.* variables for geolocation data in all new and existing Fastly services. Additional details have been emailed to known impacted customers from Fastly Customer Support. If you have any questions or concerns you can contact Fastly’s Support team at support@fastly.com.

Maintenance will begin as scheduled in 60 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

We are aware of a possible issue and are working to determine the scope and impact.

We have become aware of an issue where geolocation data may return blank responses for some customers. Our engineering teams are investigating and will provide more information as soon as possible.

We are continuing to work on a fix for this issue.

A mitigation has been identified and is in progress.

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

This incident has been resolved.