Resolved

The previously reported concern with email delivery has been resolved. The service is fully restored and there is no longer an impact to customers. This incident is resolved.

Update

Between 20:15 and 21:15 UTC, customers provisioned on EMEA based infrastructure may have experienced issues sending and receiving emails. The underlying issue has now been resolved. Any emails queued on the customer side should start delivering based on the customer’s retry schedule.

As of 21:15 UTC, all customers globally are no longer impacted and we continue to closely monitor the service.

We will provide our next update on April 3, 2020 at 20:00 UTC, or as new information is discovered.

Monitoring

As of approximately 20:03 UTC, we have applied mitigation and emails are processing normally. Any email queued on the customer’s side should start being delivered based on the customer's retry schedule.

Our engineers are working on identifying the cause of this issue and will continue to closely monitor the email traffic to ensure smooth service operation.

We will provide our next update on April 3, 2020 at 20:00 UTC or as new information is discovered.

Update

This issue is impacting both inbound and outbound emails for our customers. Customers sending or receiving emails from impacted US East infrastructure may continue to receive ‘450-Requested action aborted [9] 406-2’ error message.

Note that only half of the US infrastructure is impacted by this issue. The remaining infrastructure continues to process email traffic without an issue.

Our engineers are in the process of taking the impacted infrastructure out of service and continue to be actively engaged as we work towards service restoration.

We will provide an update at 21:00 UTC, or as soon as more information becomes available.

Investigating

We are aware of a small subset of customers provisioned on US based infrastructure experiencing issues receiving emails. Impacted customers may receive an error message “450-Requested action aborted [9] 406-2”

We are handling this issue as a high priority and have engaged all appropriate teams at Broadcom. Please note that there is no impact to protection services, and all other aspects of our services remain functional.

We will provide an update at 20:00 UTC or as soon as more information becomes available.

Began at:

Affected components