Changes / Omni Analytics / Error loading pages in Omni - Something went wrong 500:Error
Omni Analytics: Major incident: Error loading pages in Omni - Something went wrong 500:Error
Summary
Omni Analytics reported a major EastUsa outage causing page-loading 500 errors and query-processing delays from 2026-02-18 15:05 UTC to 2026-02-18 18:06 UTC, lasting 3 h 1 min. An infrastructure scaling event destabilized the job-processing pipeline; a stuck transaction blocked backend work. Cycling the affected component restored service, and all backlogs cleared.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Error loading pages in Omni - Something went wrong 500:Error
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-02-18 15:05 UTC
Before: not present
After: 2026-02-18 18:06 UTC
Before: not present
After: EastUsa
Before: not present
After: Our monitoring picked up an increase in error rates and we have begun receiving some reports. We are actively investigating and working on mitigation
Before: not present
After: We identified an unhealthy resource in our infrastructure and have applied a mitigation. We are seeing error rates decrease but we are continuing to monitor and investigate.
Before: not present
After: Error rates have stayed down since our mitigation was implemented. We are continuing to monitor.
Before: not present
After: We are seeing increased application errors and are actively investigating.
Before: not present
After: Our team has identified a stuck transaction in our job queue, which was preventing work from being dispatched to our backend workers. We have cycled the affected component and are seeing recovery. Investigation continues and we will provide another update shortly.
Before: not present
After: Our mitigation efforts appear to be successful and we are seeing active recovery. We have identified the root cause as an infrastructure scaling event that introduced instability into our job processing pipeline. Queue depths are decreasing and we are continuing to monitor closely.
Before: not present
After: This incident has been resolved. Query processing has stabilized, all backlogs have cleared, and we are no longer seeing any errors or delays.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Error loading pages in Omni - Something went wrong 500:Error (this change) Omni Analytics reported a major EastUsa outage causing page-loading 500 errors and query-processing delays from 2026-02-18 15:05 UTC to 2026-02-18 18:06 UTC, lasting 3 h 1 min. An infrastructure scaling event destabilized the job-processing pipeline; a stuck transaction blocked backend work. Cycling the affected component restored service, and all backlogs cleared. | Major incident |
All Omni Analytics changes → · Omni Analytics profile · Markdown · JSON