[US][Subprocessor] Elevated 503 Responses Linked to Fastly Disruption
Incident
Report for Nylas v3
Resolved
Fastly has posted the following update on their Status Page (https://www.fastlystatus.com/incident/377443):
"A correction has been deployed to the NGWAF platform by Engineering, resulting in a phased recovery for affected customers. Deployment monitoring will persist until full service restoration is observed for all impacted services.
This incident caused disruption to customers utilizing NGWAF services; all other products and services remained operational.
Customers experiencing ongoing issues are encouraged to contact their assigned account teams or the support team through dedicated support chat or email at support@fastly.com if a case is not already in progress."
"A correction has been deployed to the NGWAF platform by Engineering, resulting in a phased recovery for affected customers. Deployment monitoring will persist until full service restoration is observed for all impacted services.
This incident caused disruption to customers utilizing NGWAF services; all other products and services remained operational.
Customers experiencing ongoing issues are encouraged to contact their assigned account teams or the support team through dedicated support chat or email at support@fastly.com if a case is not already in progress."
Update
Fastly has posted the following update on their Status Page (https://www.fastlystatus.com/incident/377443):
"Our engineers have identified the contributing factor and are applying a fix to our Next-Gen WAF (NGWAF) services."
"Our engineers have identified the contributing factor and are applying a fix to our Next-Gen WAF (NGWAF) services."
Monitoring
Some customers may be experiencing elevated 503 errors when accessing our services on API v3. This is related to an active incident at our CDN provider, Fastly. Our team is closely monitoring the situation and working to mitigate impact where possible.
You can track Fastly's progress on their Status Page here: https://www.fastlystatus.com/incident/377443
You can track Fastly's progress on their Status Page here: https://www.fastlystatus.com/incident/377443
This incident affected: Subprocessors (Fastly).