Downstream SSO provider issue may cause certain users to have issues logging in
Monitoring - We've seen no further issues and confirmed Omnea can withstand further degradation to the AWS VPC Origins feature that is currently undergoing an outage.

We've also re-routed login to avoid the degraded downstream areas so fewer users should see any IdP issues either. If you still experience login issues please reach out to support in-app (not gated by login).
Jul 16, 2026 - 11:21 BST
Update - At present, we've confirmed that the AWS Cloudfront global outage is not affecting core Omnea services outside of certain IdP login issues. Our team is continuing to monitor the downstream status in case of further degradation.
Jul 16, 2026 - 10:26 BST
Identified - The downstream provider issue is being caused by a further downstream AWS Cloudfront outage causing widespread internet outages across the globe. Our team is monitoring those incidents to minimise effect on Omnea services.
Jul 16, 2026 - 10:00 BST
Investigating - A downstream provider (https://status.workos.com/) are seeing elevated error rates. We are investigating if any Omnea users will see knock on effects. Exact impact will depend on login method and IdP used.
Jul 16, 2026 - 09:47 BST
Uptime over the past 90 days. View historical uptime.
Omnea Platform Degraded Performance
90 days ago
99.85 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jul 16, 2026

Unresolved incident: Downstream SSO provider issue may cause certain users to have issues logging in.

Jul 15, 2026

No incidents reported.

Jul 14, 2026

No incidents reported.

Jul 13, 2026
Escalated volume of task error timeouts
Resolved - Confirmed errored tasks are no longer above the expected rate. We will continue to monitor environments to ensure errored tasks are successfully retrying without intervention.
Jul 13, 13:10 BST
Monitoring - Errored traffic has been re-routed. We're monitoring to ensure failed tasks are cleared across environments.
Jul 13, 13:02 BST
Identified - Fix in progress to re-route the proportion of traffic causing escalated error volume. This should eradicate any general performance impact.
Jul 13, 12:54 BST
Investigating - Some customers are seeing an escalated number of task errors. These errors are clearing when retried, however we are investigating the root cause of the initial intermittent errors.

Most tasks should be unaffected, and any errored tasks should retry successfully shortly.
Jul 13, 12:48 BST
Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026

No incidents reported.

Jul 9, 2026

No incidents reported.

Jul 8, 2026

No incidents reported.

Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026
Network security upgrade
Completed - The scheduled maintenance has been completed.
Jul 4, 23:00 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 4, 21:00 BST
Scheduled - As part of our ongoing investment in platform security, Omnea will be performing a network configuration update during a scheduled window outside of core working hours on Saturday 4th July at 21:00 BST.

The Omnea platform will remain available throughout, but you may see brief, intermittent disruption to outbound requests from Omnea to external systems — this includes your configured integrations and any workflow steps that call external HTTP endpoints.

We've scheduled this work for a low-traffic weekend window to minimise any impact. We'll post updates here as the maintenance begins and completes.
Jun 26, 17:39 BST
Jul 3, 2026

No incidents reported.

Jul 2, 2026
Table loading timing out
Resolved - The issue has been resolved.

During routine database maintenance activity to remove legacy objects, a transaction was unintentionally left open. This resulted in locks being held on a number of database objects for data-integrity reasons, which impacted availability of certain endpoints.

The open transaction was identified, and then committed immediately, releasing the locks and restoring normal service.

We are reviewing our maintenance procedures and safeguards to reduce the likelihood of similar incidents during future operational activities.
Jul 2, 15:54 BST
Investigating - Some users are seeing their table loading timing out and therefore showing no results. We're investigating the root cause and have confirmed no underlying data is affected.
Jul 2, 15:51 BST
← Incident History Powered by Atlassian Statuspage