Resolved after 12 minutes, affecting Omnea Platform, on April 14, 2026.
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.
Affected components
Update timeline
- 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.
- resolved Apr 14, 2026, 07:59 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.
Your product runs on more than Omnea
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services