Flow Outage - OrbusInfinity South Africa

Update timeline

1. investigating Oct 01, 2026, 09:25 AM UTC

   We are currently investigating an issue affecting the OrbusInfinity South Africa node. Users in South Africa are experiencing a 500 Internal Server Error when attempting to open Flow. Our team is actively investigating the cause and will provide a further update as soon as possible.

2. identified Oct 01, 2026, 09:44 AM UTC

   We have identified the cause of the issue affecting Flow on the OrbusInfinity South Africa node and our engineers are working to restore service. A further update will be provided once service has been restored.

3. monitoring Oct 01, 2026, 10:20 AM UTC

   The issue affecting Flow on the OrbusInfinity South Africa node has been resolved and service has been restored. We are monitoring to confirm full stability.

4. resolved Oct 01, 2026, 02:55 PM UTC

   The issue affecting Flow on the OrbusInfinity South Africa node has been fully resolved. Service has been stable since 10:12 UTC (12:12 SAST) and we are satisfied that full service has been restored.

5. postmortem Oct 16, 2026, 04:51 PM UTC

   ## Incident Summary On 1 October 2026, Flow was unavailable to users in the South Africa region between 08:44 UTC \(10:44 SAST\) and 10:12 UTC \(12:12 SAST\). The issue occurred when a scheduled update to Flow was deployed and could not complete, because messaging components that Flow depends on were not in place in the region following its recent migration. The missing components were created, the update was redeployed and Flow was available again at 10:12 UTC \(12:12 SAST\). After a period of monitoring, the incident was resolved at 14:55 UTC. ## Impact Users in the South Africa region could not open Flow for the duration of the incident. Running Flow integrations were not affected, other OrbusInfinity functionality was not affected, and no other regions were affected. ### Regions Affected * South Africa ### User Experience * When users tried to open Flow, the Flow panel loaded blank or returned a 500 Internal Server Error. * Running Flow integrations continued to operate normally. ## Root Cause Analysis The South Africa region had recently been migrated to the new hosting platform during planned maintenance. As part of the migration, new messaging components were set up for the region. Some of the components that Flow depends on are created when a separate OrbusInfinity service is deployed. Each time Flow is deployed, it connects to these components, and the deployment cannot complete if they are not present. During the migration activities, the deployment pipelines did not yet enforce this dependency, and the service that creates these components was not redeployed after the new messaging setup was in place. As a result, the components that Flow depends on were not created. Flow continued to run normally until 1 October 2026, when the first update to Flow since the migration was deployed. The update could not connect to the missing components, so it could not complete, and Flow was unavailable until the issue was resolved. ### Resolution The service responsible for creating the messaging components was deployed, which created the missing components in the South Africa region. The Flow update was then redeployed so that it could connect to them, and Flow was available again at 10:12 UTC \(12:12 SAST\). The region was monitored until the incident was resolved at 14:55 UTC. The following changes have been made to address this issue: * Explicit dependencies have been added to the deployment pipelines, so that the messaging components must be in place before the services that depend on them are deployed. * All regions already on the new hosting platform have been checked to confirm that the required messaging components are present.