# 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, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-02-18 15:05 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/0zjq5lz8546d](https://stspg.io/0zjq5lz8546d)
- [Company: Omni Analytics](https://rewindex.com/company/omni-analytics.md)
- Versions: before (none: first archived) → after incident\_version:74/j200rz0s30sd@584d0c112fd5
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Error loading pages in Omni - Something went wrong 500:Error
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-02-18 15:05 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-02-18 18:06 UTC
```

**6. Added: Affected components**

```diff
+ EastUsa
```

**7. Added: Update** (investigating) · 2026-02-18 15:05 UTC

```diff
+ Our monitoring picked up an increase in error rates and we have begun receiving some reports. We are actively investigating and working on mitigation
```

**8. Added: Update** (investigating) · 2026-02-18 15:08 UTC

```diff
+ 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.
```

**9. Added: Update** (monitoring) · 2026-02-18 15:21 UTC

```diff
+ Error rates have stayed down since our mitigation was implemented. We are continuing to monitor.
```

**10. Added: Update** (investigating) · 2026-02-18 16:20 UTC

```diff
+ We are seeing increased application errors and are actively investigating.
```

**11. Added: Update** (identified) · 2026-02-18 17:32 UTC

```diff
+ 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.
```

**12. Added: Update** (monitoring) · 2026-02-18 17:42 UTC

```diff
+ 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.
```

**13. Added: Update** (resolved) · 2026-02-18 18:06 UTC

```diff
+ This incident has been resolved. Query processing has stabilized, all backlogs have cleared, and we are no longer seeing any errors or delays.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-02-18 15:05 UTC | Major incident: Error loading pages in Omni - Something went wrong 500:Error (this change) | outage |

All Omni Analytics changes: [timeline](https://rewindex.com/company/omni-analytics/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i40d8fc7ff69b5e · Markdown: https://rewindex.com/change/i40d8fc7ff69b5e.md · JSON: https://rewindex.com/api/v1/changes/i40d8fc7ff69b5e · Generated 2026-10-18T02:31:27.590Z