We are investigating elevated errors to our configuration features within our Security Console & API services.

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Security Console & API.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Security Console & API services has been mitigated.

Engineering has confirmed that configuration features within our Security Console & API services has been fully restored. Customers may have experienced 404 errors when enabling, disabling, or configuring security protection features from the 3rd of December 2024 at 17:00 to the 4th of December 2024 at 16:19 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: 2024-12-04 16:38:03 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.

Fastly Engineers detected a performance impacting event affecting the Security Console & API service.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly Engineers detected a performance impacting event affecting our Next-Gen WAF (NGWAF) Dashboard.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

We are investigating elevated errors to our Next-Gen WAF (NGWAF) Dashboard.

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Next-Gen WAF (NGWAF) Dashboard.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Next-Gen WAF (NGWAF) Dashboard has been mitigated.

Engineering has confirmed that our Next-Gen WAF (NGWAF) Dashboard has been fully restored. Customers may have experienced agents showing as offline and received alerts that agents are offline from 18:00 on October 29, 2024 to 21:35 on October 30, 2024 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-10-30 20:58:52 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 observed an unplanned event that contained impact to Dashboard Data for Edge WAF customers.

This event is resolved, and there is no remaining impact.

Customers may have experienced a gap in the data in their Edge WAF service dashboards from 00:00 to 00:40 UTC. (~40 minutes) Our investigation into this incident confirms that customer Edge WAF services experienced no disruption, and that this incident only impacted data propagation on the dashboard within the Console.

Customers may have experienced impact to varying degrees during the times outlined above.

Please engage with our Support team through https://support.fastly.com if you have any questions and/or concerns.

We are investigating data display issues within our Dashboard Data service.

Our engineers have identified the contributing factor and are applying a fix to our Dashboard Data service.

Engineering has confirmed the impact to our Dashboard Data service has been mitigated.

Engineering has confirmed that our Dashboard Data service has been fully restored. Customers may have experienced data display issues from 14:12 to 17:47 UTC.

This incident is resolved.

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

We are investigating elevated errors to our Dashboard Data service.

Our engineers are continuing to investigate elevated errors to Dashboard Data service.

Our engineers have identified the contributing factor and are applying a fix to our Dashboard Data service.

All other locations and services are unaffected.

Engineering has tested and confirmed a fix that is being gradually deployed to restore Dashboard Data services. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Customers with questions may reach out to our support team through https://support.fastly.com. 

Our network availability and all other services are unaffected by this incident.

Engineering has confirmed that Dashboard Data services have been fully restored. Customers may have experienced missing data on the overview page from 06:00 to 21:36 UTC.

This incident is resolved.

We are investigating elevated errors to our Dashboard Data. 

Our engineers have identified the contributing factor and are applying a fix to our Dashboard Data.

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

Engineering has confirmed that Dashboard Data has been fully restored. Customers may have experienced dashboard loading failures and login issues from 19:30 on the 13th of May to 12:07 on the 14th of May UTC.

This incident is resolved. 

We are investigating elevated errors from Advanced Rate Limiting (ARL) on EdgeWAF services.

Our engineers have identified the contributing factor and are applying a fix to our Advanced Rate Limiting (ARL) on EdgeWAF services. 

Engineering has confirmed the impact to our Advanced Rate Limiting (ARL) on EdgeWAF services has been mitigated.

Engineering has confirmed that our Advanced Rate Limiting (ARL) on EdgeWAF services has been fully restored. Customers may have experienced rules being applied to additional requests post match, that should not be rate limited from 17:50 to 20:15 UTC.

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

This incident is resolved.