Connect Ordinary Flows (US Region)

Update timeline

1. investigating Mar 04, 2026, 03:52 PM UTC

   We are currently investigating an issue affecting Connect Ordinary Flows on our US instance. Due to a service disruption with our upstream cloud provider in the US East (Ashburn) region, new containers are currently unable to launch. Please note that all incoming messages are being securely held in our queues. No data is being lost, and processing will resume automatically once the connection is restored. Our engineering team is working closely with the provider to expedite a resolution. We will provide further updates as more information becomes available.

2. investigating Mar 04, 2026, 04:25 PM UTC

   We are continuing to work with the provider on full resolution for all affected services. We will provide updates as they become available.

3. investigating Mar 04, 2026, 04:55 PM UTC

   We are continuing to work with the provider for a resolution. We will provide updates as they become available.

4. investigating Mar 04, 2026, 05:30 PM UTC

   We are continuing to work with the provider on full resolution for all affected services. We will provide updates as they become available.

5. identified Mar 04, 2026, 05:57 PM UTC

   We are seeing partial restoration at this time and are monitoring closely.

6. monitoring Mar 04, 2026, 06:36 PM UTC

   Ordinary Flows are beginning to operate now. We continue to monitor the progress closely while working to full resolution.

7. monitoring Mar 04, 2026, 07:03 PM UTC

   Our engineering team continues to monitor and work with the provider for resolution. We will continue to provide updates as more information becomes available.

8. monitoring Mar 04, 2026, 07:33 PM UTC

   We are continuing the monitoring, but seeing better results. We will provide further updates as more information becomes available.

9. monitoring Mar 04, 2026, 08:00 PM UTC

   We are continuing the monitoring, but seeing better results. We will provide further updates as more information becomes available.

10. monitoring Mar 04, 2026, 08:30 PM UTC

    We are continuing the monitoring, but seeing better results. We will provide further updates as more information becomes available.

11. monitoring Mar 04, 2026, 09:33 PM UTC

    We are continuing to work with our provider for full resolution. We will provide further updates as more information becomes available.

12. monitoring Mar 04, 2026, 10:30 PM UTC

    Our vendor has indicated that the platform should now be fully operational. We will continue to monitor to confirm resolution, and provide updates as more details become available.

13. resolved Mar 04, 2026, 10:57 PM UTC

    Squiz teams have worked with our 3rd party service provider, and a fix has been deployed for the current Incident. This restored service for all affected customers. We apologise for this degradation of service and thank you for your patience while we worked on the resolution. A postmortem will be provided via https://status.squiz.cloud once we have worked with our service provider.