Omni Analytics change history

Omni Analytics reported a critical incident affecting Ireland: server timeouts caused 500 errors on EU instances. It started at 2026-08-27 14:52 UTC and was resolved at 2026-08-27 15:47 UTC, lasting 55 min; the vendor reported that one model service spiked and began recovering.

Omni Analytics reported a major outage in EastUsa and Ireland, with pages returning `Application DB Error` from 2026-05-07 01:44 UTC until resolution at 2026-05-07 03:11 UTC (1 h 26 min). A scheduled internal database table update caused full page errors; a fix completed the update safely.

Omni Analytics reported critical Omni App slowness and occasional errors affecting EastUsa and Ireland, starting 2026-02-25 18:44 UTC and lasting 38 min until resolution at 2026-02-25 19:22 UTC. A recent change caused performance degradation; the team rolled back to a previous deployment, and all systems returned to operational status.

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.

Omni Analytics reported a major incident affecting access and causing slowness in Ireland from 2025-12-04 09:15 UTC to 2025-12-04 17:12 UTC, lasting 7 h 57 min. Certain configurations with very large numbers of model extensions could trigger an internal database query that exhausted resources; mitigation was stable at resolution, with a permanent fix in development.

Omni Analytics reported major query execution delays in EastUsa from 2025-10-20 14:20 UTC to 2025-10-21 00:18 UTC, lasting 9 h 58 min. Cloud-provider infrastructure issues caused a query backlog; rerunning queries did not speed execution. Omni added resources and confirmed stable service before resolving the incident.

Omni Analytics reported a major outage affecting EastUsa and Ireland, with full-page errors for users of advanced dbt and connection environment features caused by a recent code change. The incident ran from 2025-09-11 20:56 UTC to 2025-09-11 21:39 UTC (43 min); a fast rollback restored normal function by 21:07 UTC.

Omni Analytics pages in EastUsa were inaccessible during a critical incident from 2025-09-08 17:57 UTC to 2025-09-08 19:15 UTC, lasting 1 h 18 min. A recent code change generated unexpectedly large database queries that saturated CPU resources, causing query timeouts and connection failures; Omni reverted the change and resolved the incident.

Omni Analytics reported a major outage affecting Google authentication and some Google BigQuery queries across Australia, Canada, EastUsa, and Ireland, starting 2025-06-12 18:23 UTC and lasting 5 h 11 min. Google Cloud interruptions caused access failures; recovery load also hung requests, prompting added infrastructure resources. The incident resolved at 2025-06-12 23:34 UTC.

Omni Analytics reported a major degradation causing slow responses in the US region (EastUsa), from 2025-04-29 16:39 UTC to 2025-04-29 22:10 UTC, lasting 5 h 30 min. A model validation process repeatedly called an inefficient library function, exhausting memory in some US East infrastructure; the deployed fix removed those calls and was validated to resolve the memory exhaustion.

Omni Analytics reported a major incident in EastUsa: some customers saw error pages on a subset of embedded dashboards from 2025-02-22 00:28 UTC to 2025-02-22 01:50 UTC, lasting 1 h 22 min. A new route was not enabled in embedded contexts; Omni rolled back the change and noted a page refresh might be required.

Omni Analytics reported a major incident affecting EastUsa, with intermittent errors in the web application and query execution from 2025-02-14 21:58 UTC to 2025-02-14 22:10 UTC (11 min). A network component upgrade caused intermittent connectivity problems; the change was rolled back and the incident resolved.

Omni Analytics reported a major incident affecting EastUsa: intermittent US-region network errors caused error:500 "Something went wrong" messages; refreshing could help. It started at 2025-01-27 18:13 UTC and was resolved at 2025-01-28 01:11 UTC, lasting 6 h 57 min. The vendor identified the source but did not specify the cause or fix.

Omni Analytics reported a critical East USA outage affecting model and query loading: reports and new analyses loaded slowly or failed. The incident ran from 2024-10-18 15:08 UTC to 2024-10-18 20:50 UTC, lasting 5 h 41 min. The issue was isolated and mitigated by 16:02 UTC, and the service subsequently remained stable.

Omni Analytics reported a critical East USA incident: reports and new analyses loaded slowly or failed to load from 2024-10-17 20:46 UTC until 2024-10-17 23:43 UTC, lasting 2 h 57 min. A fix was applied at 10-17 22:19 UTC; the vendor said it would perform a root cause analysis and take steps to prevent recurrence.

Omni Analytics reported major degraded performance in EastUsa, with most queries failing to complete. The incident ran from 2024-04-09 18:44 UTC to 2024-04-10 01:04 UTC (6 h 19 min). Queries against a specific database type exhausted memory, repeatedly crashing querying until cancelled; Omni identified a fix for release that day and later marked the incident resolved.

Omni Analytics reported major query degradation in EastUsa from 2024-04-08 16:55 UTC to 2024-04-08 17:05 UTC, lasting 10 min. Queries were slow or delayed because an information-schema query spike after cache expiration triggered a thundering herd, compounded by missing autoscaling logic; the incident was resolved, with autoscaling improvements planned.