Is Orbus Software down?

We are investigating reports that users in the OrbusInfinity Government (FedRAMP) region receive a 500 Internal Server Error when accessing Draw. Affected Regions: OrbusInfinity Government (FedRAMP) Affected Components: OrbusInfinity Draw

The fix has been successfully deployed to the OrbusInfinity Government (FedRAMP) environment and service has been restored. We will monitor the system for a period prior to confirming incident closure.

After a period of monitoring, the OrbusInfinity Draw component is stable. The incident is being marked as resolved.

We have identified an issue affecting the waffle menu in OrbusInfinity in some regions. When accessing the waffle menu, users receive a "No Access" message rendering the menu inaccessible. The cause has been identified and a fix is being progressed. We will provide a further update once the fix has been confirmed and service has been restored. Affected Regions: - UAE - Qatar - IRAP (partial - not all users affected)

We have identified the cause of this issue and a fix is currently being developed. To prevent further disruption, the fix will be deployed outside of core business hours. In the meantime, whilst the waffle menu is inaccessible, the items contained within remain accessible via the following methods: SharePoint: Accessible via your direct SharePoint link. SharePoint is owned and operated by your organisation. Solutions Hub: Accessible via your direct Solutions Hub URL. If you do not know your Solutions Hub URL, please contact our support team directly: [email protected] / support.orbussoftware.com Visio Desktop: Visio can be opened and used directly as normal. Visio Add-In: Download links are available in our knowledge base: Install OrbusInfinity Visio Add-in Affected Regions: - OrbusInfinity UAE North - OrbusInfinity Qatar Central - OrbusInfinity Australia IRAP (partial - not all users affected) Next Update: Following successful deployment of the fix to each region.

We have successfully deployed the fix to the OrbusInfinity Government (IRAP) environment and waffle menu functionality has been restored for all affected users in this region. The same fix will be deployed to OrbusInfinity UAE and Qatar outside of core business hours to minimise disruption. We will provide a further update following successful deployment to each region. Regions Restored: - IRAP Regions Pending Fix: - UAE - Qatar Next Update: Following successful deployment of the fix to UAE North and Qatar Central.

The fix has been successfully deployed to OrbusInfinity UAE and Qatar. Waffle menu functionality has been restored across all affected regions and is operating normally. Regions Restored: - IRAP - UAE - Qatar

We are currently investigating an issue affecting Flow in the OrbusInfinity UK, Europe, and Australia regional nodes. Users in these regions may be unable to access the Flow menu at this time. We are actively investigating the cause and will provide a further update as soon as possible. Affected Regions: - UK - Europe - Australia

We have identified the cause of this incident and a fix is currently being deployed to all impacted regions. We will provide a further update once the fix has been confirmed and service has been restored.

Flow access has been restored across all affected regions and is operating normally. We will monitor for a period prior to closing the incident.

Resolved - We have completed our monitoring period and are satisfied that the incident has been fully resolved. The in-app Flow menu flyout is operating normally across all affected regions. A full post-incident report will be published in due course.

We are currently investigating an issue affecting dashboards on the OrbusInfinity South Africa node. Users in this region are experiencing failures when attempting to load dashboards - "Something Went Wrong". Our team has been engaged and is actively investigating the root cause. Further updates will be provided as the investigation progresses.

Dashboards have been restored on the OrbusInfinity South Africa node. Service is now confirmed accessible.

## Incident Summary On 2 October 2026, Dashboards within OrbusInfinity was unavailable to users in the South Africa region between 10:27 UTC \(12:27 SAST\) and 10:48 UTC \(12:48 SAST\). The issue occurred during a scheduled update to the Dashboards service. The update included a network configuration step, which took longer than expected to complete. Dashboards was available again at 10:48 UTC \(12:48 SAST\), once the update had completed. ## Impact Users in the South Africa region could not load Dashboards for approximately 21 minutes. Other OrbusInfinity functionality was not affected, and no other regions were affected. ### User Experience * Users received a "Something went wrong" error when trying to load Dashboards. ## Root Cause Analysis An update to Dashboards was deployed to the South Africa region. The update included a change to the network configuration that Dashboards uses to connect to other platform components. Dashboards could not be reached while this step was in progress. The change was expected to take effect almost immediately, but in the South Africa region it took around 20 minutes to propagate. Dashboards became available again once the step had completed. ### Resolution Dashboards was available again at 10:48 UTC \(12:48 SAST\), when the update completed. No further action was needed to restore service. The following change has been made to address this issue: * Updates that include network configuration changes, or other changes that could affect availability, are now carried out in an out-of-hours maintenance window.

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.

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.

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.

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.

## 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.