Third Party Service Provider
We're investigating possible performance impact affecting the Support Chat System related to a vendor reported incident.
- Vendor status page: https://slack-status.com/2025-02/1b757d1d0f444c34
Customers may experience failed support case functions when attempting to generate a support case from Support Chat systems. We ask that customers email Support teams at support@fastly.com to ensure no delays.
Slack Status Updates
Slack is actively working to resolve the issue and is providing updates on the incident status at the following link: Slack Status. We encourage you to monitor this page for the latest information.
Impact on Our Services
While we are closely monitoring the Slack incident, we want to assure you that our ability to provide customer support and the accessibility of our Network remain unaffected. We have implemented our established communication protocols to ensure continuity of support during this vendor outage. All other products and services are also operating normally and are not impacted by this incident.
Slack has successfully addressed their incident and reported that all services have been restored.
We are conducting internal tests on Support Chat Systems to verify that all functions are operating properly.
The vendor has confirmed a second event impacting Support Chat Systems.
- We are monitoring their updates here: https://slack-status.com/2025-02/d41e4bfd1ccae26a
Customer should continue to request support through email, via support@fastly.com
This incident has been resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-02-26 16:50:53 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'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.
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.