Middleware service disruption

This incident has been resolved.

A fix has been implemented and we are monitoring the results. It is expected that all functionality has been restored in the Connect application.

We are continuing to work on bringing our parallel middleware environment online and restoring full service.

Our engineering and DevOps teams are actively working on deploying a parallel middleware environment to bypass the current infrastructure constraint and restore service. We are focused on getting the Connect message composer back to full functionality as quickly as possible.

Our DevOps and engineering teams, in coordination with our cloud service provider, are continuing to actively work toward a resolution for the middleware infrastructure disruption. We are fully focused on restoring normal operations as quickly as possible and will provide our next update in 60 minutes, or sooner if additional information becomes available.

Our engineering teams are continuing to investigate the infrastructure disruption affecting our core middleware services. Connect users may experience errors when attempting to access the message composer, processing group bulk actions, or utilizing the file upload feature. We are actively working with our cloud infrastructure provider to restore full service in the Connect application.

We appreciate your patience as we work through this and will provide our next update in 30 minutes or when new information becomes available.

We are currently experiencing an infrastructure disruption within our core middleware services on our platform. This directly impacts the Connect application, preventing the message composer from loading.

The ability to compose and send new messages is temporarily degraded. Users may experience loading errors or blank screens when opening the composer. Please note that data integrity is unaffected; all historical messages, draft data, and user records remain secure.

Our DevOps and engineering teams have successfully isolated the backend service constraint. We are actively working alongside our cloud service provider to deploy a fix and restore normal middleware routing. We will continue to provide updates every 30 minutes until full service is restored.