Omnea Outage History

Started Oct 29, 2026, 05:34 PM UTC· resolved Oct 29, 2026, 07:32 PM UTC

1. identified Oct 29, 2026, 05:34 PM UTC

   A third party provider, WorkOS, are reporting degraded API performance that can be tracked at status.workos.com Organisations using SSO login may experience delays authenticating or multiple login attempts being required. We have not yet identified any wider impact.

2. monitoring Oct 29, 2026, 06:13 PM UTC

   WorkOS have resolved their issue and are now monitoring performance.

3. resolved Oct 29, 2026, 07:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 16, 2026, 08:47 AM UTC· resolved Jul 16, 2026, 01:44 PM UTC

1. investigating Jul 16, 2026, 08:47 AM UTC

   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.

2. identified Jul 16, 2026, 09:00 AM UTC

   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.

3. identified Jul 16, 2026, 09:26 AM UTC

   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.

4. monitoring Jul 16, 2026, 10:21 AM UTC

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

5. resolved Jul 16, 2026, 01:44 PM UTC

   The downstream AWS Cloudfront outage has been marked as resolved. Monitoring confirmed no further effect on the Omnea platform.

Read the full incident report →

Started Jul 13, 2026, 11:48 AM UTC· resolved Jul 13, 2026, 12:10 PM UTC

1. investigating Jul 13, 2026, 11:48 AM UTC

   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.

2. identified Jul 13, 2026, 11:54 AM UTC

   Fix in progress to re-route the proportion of traffic causing escalated error volume. This should eradicate any general performance impact.

3. monitoring Jul 13, 2026, 12:02 PM UTC

   Errored traffic has been re-routed. We're monitoring to ensure failed tasks are cleared across environments.

4. resolved Jul 13, 2026, 12:10 PM UTC

   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.

Read the full incident report →

Started Jul 02, 2026, 02:51 PM UTC· resolved Jul 02, 2026, 02:54 PM UTC

1. investigating Jul 02, 2026, 02:51 PM UTC

   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.

2. resolved Jul 02, 2026, 02:54 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 04:11 PM UTC· resolved May 26, 2026, 04:16 PM UTC

1. investigating May 26, 2026, 04:11 PM UTC

   Some pages are showing degraded loading speeds which is preventing some workflows and tasks from loading. We're identifying the root cause to rectify quickly.

2. resolved May 26, 2026, 04:16 PM UTC

   Issue resolved by fixing a parallel query conflict.

Read the full incident report →

Started May 08, 2026, 02:45 PM UTC· resolved May 08, 2026, 03:36 PM UTC

1. identified May 08, 2026, 02:45 PM UTC

   An upstream database provider is experiencing a partial outage (https://hasura-status.com/) - some users in Omnea may experience degraded table loading performance whilst traffic is re-routed. We will update once we know more.

2. monitoring May 08, 2026, 03:21 PM UTC

   The upstream provider have indicated they have applied a fix and are seeing recovery. We will continue to monitor loading performance in Omnea.

3. resolved May 08, 2026, 03:36 PM UTC

   Performance confirmed to have recovered.

Read the full incident report →

Started Apr 20, 2026, 05:33 AM UTC· resolved Apr 20, 2026, 06:04 AM UTC

1. investigating Apr 20, 2026, 05:33 AM UTC

   We’re aware of reports of login issues affecting some users and are currently investigating.

2. investigating Apr 20, 2026, 05:58 AM UTC

   We are continuing to investigate this issue. A possible root cause has been identified and a fix is being applied.

3. monitoring Apr 20, 2026, 06:03 AM UTC

   The environments seeing elevated login issues have returned to usual behaviour. We will update this log with a full root cause once reviewed.

4. resolved Apr 20, 2026, 06:04 AM UTC

   The incident has been resolved. Incident Summary: As part of a planned security update at 00:00 BST on Monday 20th April, the Omnea Security team determined the need to conduct a Maintenance period at 00:30 BST. In order to keep this Maintenance window outside of Business hours, and due to an anticipated lack of impact on availability, a decision was made to schedule this immediately at 00:40 BST. The Maintenance upgrade initially appeared successful and initial checks suggested normal operation. A set of manual tests carried out at 01:30 BST suggested the service was still accessible to users, however at this time there was propagating fault that would begin to affect an initially small subset of users depending on which servers their requests would be routed to. One component of the change took significantly longer than expected to fully apply — and during this window, the platform continued to serve some traffic normally while other requests encountered errors, depending on which internal services handled the request. This partial state masked the underlying issue. When the delayed component eventually completed its shutdown, additional database connectivity was lost, causing broader service impact. A subset of users therefore experienced intermittent errors and degraded performance. The issue was caused by this unexpected delay in how underlying infrastructure changes propagated, which created an unstable database connectivity state that was not immediately visible to our monitoring systems. At 06:33 BST Omnea Support identified escalated error rates as a larger volume of users began to login, and alerted “Out of Hours” support. The root cause was identified at 06:58 BST, and the fix applied with full service restored at 07:04 BST. Root Cause Analysis: Networking route tables were removed and not recreated across the VPC, breaking VPC-x-VPC connectivity with Hasura Cloud gradually as instances lost connectivity to the Database.

Read the full incident report →

Started Apr 14, 2026, 07:43 AM UTC· resolved Apr 14, 2026, 07:55 AM UTC

1. investigating Apr 14, 2026, 07:43 AM UTC

   Some pages within Omnea are experiencing degraded loading resulting in timeouts for some users. We're investigating the root cause and will update shortly.

2. resolved Apr 14, 2026, 07:55 AM UTC

   Loading timeouts were being caused due to consistently retrying authentication calls unsuccessfully in a selection of environments. This has been mitigated. We will update with a root cause once fully investigated. Cause & Mitigation: There was a missing NextJS asset in some Omnea environments in the most recent deployment. This was caused by an AWS S3 internal server error during bulk resource upload. SST Custom Resource Handler v2 handles retries for most failure modes, but not AWS internal errors - instead of aborting the deploy, it continued which led to missing assets that prevented the frontend from loading. As mitigation we will migrating NextJS to SSTv4 which will handle an AWS internal server error more elegantly.

Read the full incident report →

Started Mar 10, 2026, 02:37 PM UTC· resolved Mar 10, 2026, 02:47 PM UTC

1. investigating Mar 10, 2026, 02:37 PM UTC

   Users are having issues authorising when signing in. We're investigating the root cause.

2. resolved Mar 10, 2026, 02:47 PM UTC

   The issue is resolved. A spike in authorization requests exceeded our configured throughput limit. We intentionally throttled this spike due to pre-configured limits, however the requests failed to recover correctly because that failure was cached, which prolonged the impact until those instances were restarted. We have now mitigated the issue by deploying a follow-up change to ensure startup configuration failures are retried safely rather than persisted.

Read the full incident report →

Started Feb 26, 2026, 12:45 PM UTC· resolved Feb 26, 2026, 12:46 PM UTC

1. investigating Feb 26, 2026, 12:45 PM UTC

   We are currently investigating the cause of this issue.

2. resolved Feb 26, 2026, 12:46 PM UTC

   Issue has been resolved. The errors were related to a small selection of IP addresses - no discernible external impact.

Read the full incident report →

Started Feb 16, 2026, 04:12 PM UTC· resolved Feb 16, 2026, 04:30 PM UTC

1. identified Feb 16, 2026, 04:12 PM UTC

   Users are seeing escalated page load failures. We have already identified the issue and have a resolution fix in progress.

2. resolved Feb 16, 2026, 04:30 PM UTC

   The failure cause has been resolved. This issue was caused by an application version mismatch during deployment, where a frontend change deployed before dependent backend configuration updates had fully applied. That created a temporary incompatibility between the frontend and backend, which resulted in errors for authenticated users to access their own data. We mitigated the issue by reverting the change and have now implemented tighter deployment staging controls, compatibility validation for dependent changes, and faster rollback mechanisms to prevent recurrence and shorten future recovery time.

Read the full incident report →

Started Jan 14, 2026, 04:52 PM UTC· resolved Jan 14, 2026, 05:00 PM UTC

1. monitoring Jan 14, 2026, 04:52 PM UTC

   We've identified an issue when uploading or downloading certain documents from the platform. A fix is already deployed. We're monitoring for repeats.

2. resolved Jan 14, 2026, 05:00 PM UTC

   Confirmed as resolved. This was a short lived issue where over zealous security screening on uploaded documents was timing out and rejecting the upload. The timeout issue was resolved by additional pre-flagging of safe patterns.

Read the full incident report →

Started Dec 15, 2025, 09:30 PM UTC· resolved Dec 15, 2025, 09:30 PM UTC

1. resolved Dec 15, 2025, 09:30 PM UTC

   Some users experienced intermittent “Internal Server Error” responses when loading pages with high resource load. These errors disappeared on refresh but then would reappear intermittently on similar pages. On investigation these page load errors were caused by the frontend application exhausting a resource limit in our hosting environment when under high load. We have implemented a memory boost whilst investigating where to remove load. The errors have now abated.

Read the full incident report →

Started Dec 05, 2025, 09:07 AM UTC· resolved Dec 05, 2025, 11:01 AM UTC

1. identified Dec 05, 2025, 09:07 AM UTC

   Cloudflare are investigating API Service issues (https://www.cloudflarestatus.com/). This may affect Customer login, depending on the identity and access management solution used.

2. monitoring Dec 05, 2025, 09:27 AM UTC

   Cloudflare have indicated their incident is resolved. We are monitoring to ensure return to full operation for all users.

3. resolved Dec 05, 2025, 11:01 AM UTC

   Confirmed no further knock-on effects.

Read the full incident report →

Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 01:05 PM UTC

1. identified Oct 20, 2025, 07:00 AM UTC

   A regional AWS outage has affected certain parts of the Omnea service. Whilst the Omnea main platform functionality is still running, functionality that leverages third-party services such as SSO, notifications, and file imports, are currently experiencing degraded performance.

2. monitoring Oct 20, 2025, 09:40 AM UTC

   The AWS regional outage continues to recover. Third-party services such as SSO login functionality has now been restored, and most users should be able to sign in as normal. There will likely be a backlog of notifications and processing caused by this disruption, so we will continue to monitor, and provide another update once all systems are confirmed as fully operational.

3. monitoring Oct 20, 2025, 09:45 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 20, 2025, 01:05 PM UTC

   Monitoring has shown no further degradation. The third-party services affected by the AWS outage are showing a return to operational status.

Read the full incident report →

Started Sep 04, 2025, 09:44 AM UTC· resolved Sep 04, 2025, 12:55 PM UTC

1. identified Sep 04, 2025, 09:44 AM UTC

   We have identified some degraded performance in isolated parts of the platform when loading certain configuration pages. This can lead to taking additional time to load the page, or needing to refresh the page entirely due to timeout depending on user network speed. We are working with a third-party database provider to resolve this issue.

2. monitoring Sep 04, 2025, 10:30 AM UTC

   A fix has been implemented and we are monitoring the results to ensure continued good performance.

3. resolved Sep 04, 2025, 12:55 PM UTC

   All pages are showing a consistent return to full performance.

Read the full incident report →

Started Aug 19, 2025, 02:46 PM UTC· resolved Aug 19, 2025, 06:10 PM UTC

1. identified Aug 19, 2025, 02:46 PM UTC

   We have identified degraded performance with a third-party database provider that is causing some app pages to load more slowly or timeout entirely depending on network speed.

2. monitoring Aug 19, 2025, 03:37 PM UTC

   Performance with the third-party provider has been resolved. We're monitoring the Omnea platform performance to ensure the fix reflects on all pages.

3. resolved Aug 19, 2025, 06:10 PM UTC

   All pages are showing a return to full performance. This incident is now resolved.

Read the full incident report →

Started May 15, 2025, 10:06 AM UTC· resolved May 15, 2025, 11:06 AM UTC

1. investigating May 15, 2025, 10:06 AM UTC

   We are currently investigating an issue where emails are not being sent or are only being delivered intermittently. This may affect transactional and notification emails across our platform. We will provide an update as soon as we have more information.

2. investigating May 15, 2025, 10:34 AM UTC

   We are continuing to investigate this issue.

3. resolved May 15, 2025, 11:06 AM UTC

   We experienced an issue earlier where emails were not being sent or were only delivered intermittently. The issue has now been identified and resolved. Email delivery is back to normal. We’re continuing to monitor to ensure full stability. Thank you for your patience.

Read the full incident report →

Started Apr 04, 2025, 11:08 AM UTC· resolved Apr 04, 2025, 02:55 PM UTC

1. investigating Apr 04, 2025, 11:08 AM UTC

   We are currently experiencing degraded performance, causing some pages in our web application to fail to load. Our team is actively investigating the issue, and we will provide updates as soon as we have more information. Thank you for your patience.

2. identified Apr 04, 2025, 12:03 PM UTC

   We have identified an issue with a third-party provider which is causing degraded performance and preventing some pages in our web application from loading. We are actively working with their team on a resolution and will provide updates as soon as we have more information. Thank you for your patience while we work to restore full functionality.

3. monitoring Apr 04, 2025, 02:54 PM UTC

   The issue with our third-party provider appears to have stabilized. However, we are continuing to monitor the situation closely to ensure full recovery. We will provide further updates if we observe any recurrence. Thank you for your patience.

4. resolved Apr 04, 2025, 02:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 26, 2025, 11:32 AM UTC· resolved Mar 26, 2025, 12:58 PM UTC

1. investigating Mar 26, 2025, 11:32 AM UTC

   Our In-App Live Chat provider is having an outage. We are assisting in their investigation. In the meantime you can continue to contact our Omnea Support team directly via "[email protected]".

2. resolved Mar 26, 2025, 12:58 PM UTC

   Our provider has resolved their outage. If you still experience this issue, please try refreshing the page.

Read the full incident report →