Performance Degradation - Asynchronous Processing

As of 16:06 UTC, all stuck messages on USA222S and USA246S have cleared, and the instances are out of impact. USA222S and USA246S will be removed from this Trust posting while the team continues to restart the backend messaging service for the remaining impacted instances, and we will provide a dedicated Trust post for both USA22S and USA246S.

We’ll provide the next update when additional information becomes available.

As of 13:34 UTC, all stuck messages on USA794 have cleared, and the instance is out of impact. USA794 will be removed from this Trust posting while the team continues to restart the backend messaging service for the other impacted instances, and we will provide a dedicated Trust post for this instance.

We’ll provide the next update when additional information becomes available.

The backend messaging service for one test instance was restarted, and subsequently, it began processing the stuck messages. We will now take this action on all other impacted instances.

We’ll provide the next update when additional information becomes available.

We have finished deleting the reroute rules on one test instance; however, this has not had the desired results. As a mitigation step, additional teams are being engaged to restart a backend messaging service.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

At 18:00 UTC on April 7, 2025, customers began experiencing a performance degradation impacting asynchronous processing. Initial investigations are underway, and it appears this issue is intermittent and a result of a recent release. Teams are working to delete rerouting rules to allow messages to be processed.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.