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.

We are investigating elevated errors to our Compute and Next-Gen WAF (NGWAF) services.

All other products and services are unaffected by this incident.

Status Post, Created Date/Time: 2024-10-02 19:56 UTC 

Note: Our Customer Escalation Management team will update the start date and time of this 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 identified the contributing factor and are applying a fix to our Compute and Next-Gen WAF (NGWAF) services.

All other locations and services are unaffected.

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

Engineering has confirmed that Compute and Next-Gen WAF (NGWAF) services have been fully restored. Customers may have experienced errors when deploying Edge WAF services from 14:41 to 19:52 UTC.

This incident is resolved.

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

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

All other products and services are unaffected by this incident.

Our engineers are continuing to investigate reporting in our Next-Gen WAF (NGWAF) agent dashboard. 

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

All other locations and services are unaffected.

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

Engineering has confirmed that our Next-Gen WAF (NGWAF) agent dashboard has been fully restored. Customers using Core and Cloud WAF products may have experienced incorrect IP addresses being reported in the agent sections of the NGWAF dashboard from the 1st of October 2024 at 22:05 to the 12th of November 2024 at 20:29 UTC. 

The agent IP addresses for these customers are now being reported correctly for all online agents. Agents that are currently offline will not be updated until the agents are brought online again or they expire at which time they will be automatically removed from the agent view. 

This incident is resolved.

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

Status Post, Created Date/Time: 2024-11-12 18:51:33 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 Next-Gen WAF (NGWAF) service. 

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

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

Engineering has confirmed that Next-Gen WAF (NGWAF) service has been fully restored. Customers may have experienced seeing no data returned within their data dashboard and rules would not have been updated from 10:50 to 12:10 UTC.

This incident is resolved.

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

Fastly has identified problems with the latest release of the NGINX native module on CentOS/RHEL systems. Customers who upgrade to the latest package may have install errors related to gpg signing.

Our engineers are continuing to apply the identified fix to our Next-Gen WAF (NGWAF) service.

All other locations and services are unaffected.

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

Engineering has confirmed that Next-Gen WAF (NGWAF) service has been fully restored. Customers who attempted to install the latest released version of the NGWAF NGINX Native module on CentOS, RHEL, or Amazon Linux systems would have experienced an install error from the package manager due to gpg signing problems from17:55 to 22:32 UTC.

This incident is resolved.

Customers who did not attempt to upgrade their NGINX Native module during the period of impact were not impacted.

Only operating systems that use the yum package manager (such as CentOS, RHEL, or Amazon Linux) were impacted.

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

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.

We are investigating elevated errors for new Edge WAF deployments within our NGWAF Services.

Our network availability, existing Edge WAF and all other services are unaffected.

Our engineers have identified the contributing factor and are applying a fix to our NGWAF@Edge.

Engineering has confirmed the impact to NGWAF@Edge has been mitigated.

Engineering has confirmed that NGWAF@Edge has been fully restored. Customers may have experienced errors in new Edge WAF deployments within our NGWAF Services from 09:00 to 16:04 UTC.

This incident is resolved.

Fastly will be performing scheduled maintenance on the NextGen WAF (NGWAF). This maintenance is scheduled for 2024 April 3rd at 21:15 to 22:15 UTC (~1 hour).

No customer impact is expected.

Throughout the maintenance window, status updates will be available at the Fastly status page.

The scheduled maintenance has been completed.

We are investigating possible errors impacting our NGWAF@Edge Dashboard service. During this time, customers may see lower RPS within console than in Observability or their own metrics.

Our engineers are continuing to investigate impact to the NGWAF@Edge Dashboard service.

Engineers have identified the scope of impact for this issue, and are actively working on a mitigation strategy to fully restore the NGWAF dashboard for impacted customer services.

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

Engineering has confirmed the impact to NGWAF@Edge dashboard service has been mitigated.

This event has been resolved.