Third Party Service Provider
One of our selected vendors will be performing scheduled maintenance on our Fastly Application from 18:00 to 18:15 UTC on the 24th of April 2024.
During this maintenance window our customers may experience elevated page load errors across some of the Fastly Application views.
The scheduled maintenance has been completed.
On Tuesday, the 23rd of April 2024 from 11:30 UTC to the 24th of April 01:36 UTC, our engineers observed an unplanned event that contained impact across the Chennai (MAA), Mumbai (BOM), Kolkata (CCU), Delhi (DEL), and Hyderabad (HYD) Points of Presence (POPs) with a common transit provider.
This event is resolved, and there is no remaining impact.
We are seeing increased errors across multiple customers with origins utilizing a common cloud provider, unrelated to Fastly’s Edge Cloud Network.
The third party vendor has identified the issue and implementing a fix.
All other locations and services are unaffected.
A fix has been implemented and we are monitoring the results.
Engineering has confirmed that traffic has returned to pre-incident levels. Customers may have experienced increased errors from 23:48 to 00:55 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
Traffic in Marseille (MRS) has been temporarily rerouted.
All other locations and services are unaffected.
This issue has been identified and a fix is being implemented.
On the 24th of August at 09:15 UTC, Fastly Engineering confirmed with a third party service provider that there is an active fiber cut within the Marseille (MRS) region that is impacting connectivity to our Point of Presence (POP). We have performed standard traffic engineering practices to route our customer services away from the impacted region.
We are actively engaged with the third party service provider and are receiving routine updates as they continue to work on the issue. Once they have reported the conditions "mitigated", we will perform some tests to verify and update our status post.
For additional questions please reach out to our Support team through https://support.fastly.com.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing increased errors across multiple customers with origins utilizing a common cloud provider, unrelated to Fastly's Edge Cloud Network.
https://health.aws.amazon.com/health/status
Fastly is continuing to monitor the situation and assist as needed with related customer support inquiries.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating elevated errors in South America.
All other locations and services are unaffected
Fastly Engineering has observed elevated errors across multiple Points of Presence (POPs) in the region of South America.
This has been identified as an issue with a third party service provider unrelated to Fastly's Edge Cloud Platform, and a fix is being implemented.
All other locations and services are unaffected.
Traffic in Lima(LIM) has been temporarily rerouted.
All other locations and services are unaffected.
Fastly Engineering has applied our standard acute incident response practices and restored our LIM 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 incident has been resolved.
Fastly Engineering is currently investigating elevated errors with origins utilizing a common cloud provider in our Madrid (MAD) point of presence, unrelated to Fastly's Edge Cloud Platform.
Customers may also experience issues accessing manage.fastly.com within the impacted region.
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 investigating elevated errors in Seattle (BFI).
All other locations and services are unaffected
Traffic in Seattle (BFI) has been temporarily rerouted.
All other locations and services are unaffected.
Our investigations identified that the intermittent errors in our Seattle (BFI) POP was caused by segment testing being conducted by a third party vendor. Fastly has been in contact with the vendor to request all further testing be conducted during off-peak performance periods, later today.
The vendor has confirmed that they've normalized the circuit and have stopped all intrusive testing until further notice.
All other locations and services are unaffected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our status page vendor, StatusCast, is currently updating a recent configuration change which inadvertently disabled the filter options on https://www.fastlystatus.com/incidents.
During this time, subscribers and end users may experience an error when attempting to filter or clear filters from the "Incident History" view.
All other status page and subscriber notification services are unaffected.
We are seeing increased errors in Sao Paulo (CGH), Fortaleza (FOR) and Curitiba (CWB) data centers for Compute@Edge and NGWAF@Edge services utilizing a common network provider, unrelated to Fastly's Edge Cloud Network.
Fastly is continuing to monitor the situation and assist as needed with related customer support inquiries.
This issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Fastly Engineering has confirmed that Compute@Edge and NGWAF@Edge services in our Sao Paulo (CGH), Fortaleza (FOR) and Curitiba (CWB) data centers has been restored.
We will continue to monitor the third party network provider.
This incident has been resolved.