Netlify Status

Resolved: A fix has been deployed. We continue to monitor the system for any issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We've deployed improvements to address caching inconsistencies and are rolling out fixes to affected customers. Monitoring continues

Monitoring: We have implemented a more comprehensive fix for the caching issues and are rolling the HP Edge customers into it. We have narrowed down the root cause and are working on addressing it

Monitoring: We are continuing to monitor to ensure this issue is mitigated while we work on identifying and implementing a fix for the root cause.

Identified: We are actively monitoring to ensure this issue is mitigated while we work on identifying and implementing a fix for the root cause.

Identified: We have implemented a solution to mitigate this issue across our CDN. We are continuing to investigate the root cause.

Identified: We've identified caching inconsistencies with several sites across our HP Edge Network. We are implementing a fix to resolve this issue.

Resolved: This is now resolved.

Monitoring: We're still monitoring, however this should now be resolved.

Monitoring: During testing we noticed that a small percentage of HP edge customers are impacted as well. We've started a rollback, and are monitoring the situation.

Monitoring: We've started a rollback and are monitoring the situation

Investigating: We are seeing sporadic instances of 502 Bad Gateway responses for requests to the Standard Edge, HP Edge is not affected. Our team is investigating.

Resolved: A fix has been deployed. We continue to monitor the system for any issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We've deployed improvements to address caching inconsistencies and are rolling out fixes to affected customers. Monitoring continues

Monitoring: We have implemented a more comprehensive fix for the caching issues and are rolling the HP Edge customers into it. We have narrowed down the root cause and are working on addressing it

Monitoring: We are continuing to monitor to ensure this issue is mitigated while we work on identifying and implementing a fix for the root cause.

Identified: We are actively monitoring to ensure this issue is mitigated while we work on identifying and implementing a fix for the root cause.

Identified: We have implemented a solution to mitigate this issue across our CDN. We are continuing to investigate the root cause.

Identified: We've identified caching inconsistencies with several sites across our HP Edge Network. We are implementing a fix to resolve this issue.

Resolved: This is now resolved.

Monitoring: We're still monitoring, however this should now be resolved.

Monitoring: During testing we noticed that a small percentage of HP edge customers are impacted as well. We've started a rollback, and are monitoring the situation.

Monitoring: We've started a rollback and are monitoring the situation

Investigating: We are seeing sporadic instances of 502 Bad Gateway responses for requests to the Standard Edge, HP Edge is not affected. Our team is investigating.