Omni Analytics Outage History
Omni Analytics is up right nowPingoru has recorded 41 incidents for Omni Analytics: 17 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 4 of 720 (1%) |
| May 2026 | 3 | 12 of 744 (2%) |
| June 2026 | 1 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 2 | 4 of 744 (1%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 3 | 9 of 589 (1%) |
Incidents, newest first
Minor June 11, 2025 AI chat errors in US environment 30m EastUsa
Started Jun 11, 2025, 05:31 PM UTC· resolved Jun 11, 2025, 06:02 PM UTC
- identified Jun 11, 2025, 05:31 PM UTC
Our LLM provider is experiencing an outage that is causing errors in the AI chat experience, we are working with them to resolve the issue.
- resolved Jun 11, 2025, 06:02 PM UTC
This incident has been resolved.
Minor May 15, 2025 Intermittent page load failures 6h 7m EastUsa
Started May 15, 2025, 05:36 PM UTC· resolved May 15, 2025, 11:43 PM UTC
- investigating May 15, 2025, 05:36 PM UTC
We detected a spike in internal errors affecting some hosts. Behavior is intermittent and refreshing the page should result in successful load.
- identified May 15, 2025, 06:06 PM UTC
The issue has been identified and temporary mitigation put in place. We have not observed internal errors being surfaced in the last 20 minutes. We are continuing to monitor while we work on a longer term fix.
- identified May 15, 2025, 08:23 PM UTC
We are continuing to work on a long term fix and monitoring to ensure our mitigation is holding.
- resolved May 15, 2025, 11:43 PM UTC
This incident has been resolved. A resource intensive process was initiated during a busy period that overwhelmed a subset of our internal resources and resulted in intermittent failure to complete requests. Manual scaling of component-specific resources was needed in addition to our automated scaling to recover. We have implemented some immediate efficiency improvements and are working on implementing additional larger improvements in the coming days.
Major April 29, 2025 Slow response times in US Region 5h 30m EastUsa
Started Apr 29, 2025, 04:39 PM UTC· resolved Apr 29, 2025, 10:10 PM UTC
- investigating Apr 29, 2025, 04:39 PM UTC
Users are experiencing slow responses in the US region, our team is investigating.
- monitoring Apr 29, 2025, 05:35 PM UTC
We have mitigated the issue and are monitoring the system.
- monitoring Apr 29, 2025, 07:57 PM UTC
We have identified the root cause of the issue and are implementing a fix.
- resolved Apr 29, 2025, 10:10 PM UTC
A model validation related process triggered repeated calls to an inefficient library function that exhausted memory in a subset of our US East infrastructure. A fix has been deployed that removes calls to the inefficient library function and we have validated it resolves the memory exhaustion.
Minor April 14, 2025 Slowed Query Executions 2h 22m EastUsa
Started Apr 14, 2025, 10:13 PM UTC· resolved Apr 15, 2025, 12:35 AM UTC
- investigating Apr 14, 2025, 10:13 PM UTC
Omni is experiencing slowed query execution. We are actively addressing the issue.
- identified Apr 15, 2025, 12:00 AM UTC
We've identified the cause and we are working on a fix. You may continue to see slower-than-normal performance as we address the cause.
- resolved Apr 15, 2025, 01:56 AM UTC
A fix has been implemented, and we’re monitoring to ensure the issue is resolved.
Minor February 26, 2025 Slack outage impacting support responses and Slack deliveries 8h 47m EastUsa, Ireland, Australia, Canada
Started Feb 26, 2025, 04:59 PM UTC· resolved Feb 27, 2025, 01:47 AM UTC
- monitoring Feb 26, 2025, 04:59 PM UTC
Slack is having an outage that is impacting our ability to send and receive some support requests. For time-sensitive support issues use [email protected] until Slack becomes fully operational.
- monitoring Feb 26, 2025, 05:10 PM UTC
Some scheduled deliveries to Slack channels and users are impacted by this outage.
- monitoring Feb 26, 2025, 05:20 PM UTC
We are continuing to monitor for any further issues.
- resolved Feb 27, 2025, 01:47 AM UTC
Slack has resolved this outage: https://slack-status.com/2025-02/1b757d1d0f444c34
Major February 22, 2025 Intermittent page errors on embedded dashboards 1h 22m EastUsa
Started Feb 22, 2025, 12:28 AM UTC· resolved Feb 22, 2025, 01:50 AM UTC
- investigating Feb 22, 2025, 12:28 AM UTC
Some customers have reported seeing an error page returned for a subset of their embedded dashboards. We are actively investigating.
- identified Feb 22, 2025, 12:49 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 22, 2025, 01:29 AM UTC
A fix has been implemented and we are monitoring the results. A page refresh may be required.
- resolved Feb 22, 2025, 01:50 AM UTC
A new route was added that was not enabled in embedded contexts. We have rolled back the change.
Major February 14, 2025 Intermittent errors 11m EastUsa
Started Feb 14, 2025, 09:58 PM UTC· resolved Feb 14, 2025, 10:10 PM UTC
- investigating Feb 14, 2025, 09:58 PM UTC
Users are experiencing intermittent errors in the web application and query execution, our team is investigating.
- monitoring Feb 14, 2025, 10:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 14, 2025, 10:10 PM UTC
An upgrade to a network component caused intermittent connectivity problems, we have rolled back the change.
Major January 27, 2025 Intermittent Errors in US Environment 6h 57m EastUsa
Started Jan 27, 2025, 06:13 PM UTC· resolved Jan 28, 2025, 01:11 AM UTC
- investigating Jan 27, 2025, 06:13 PM UTC
We are experiencing intermittent network errors in the US region, our team is investigating the issue and we will provide updates as we have them.
- investigating Jan 27, 2025, 07:57 PM UTC
We are experiencing intermittent network errors in the US region. Users may see error:500 "Something went wrong" and may be able to workaround by refreshing the page. Our team is progressing towards root cause but the investigation is ongoing. We will provide updates as we have them.
- monitoring Jan 27, 2025, 08:30 PM UTC
We have identified the source of the issue and are monitoring to confirm it has been resolved.
- resolved Jan 28, 2025, 01:11 AM UTC
This incident has been resolved.