Omni Analytics Outage History

Omni Analytics is up right now

Omni Analytics had 17 outages in the last 2 years totaling 55h 52m of downtime — averaging 0.7 incidents per month.

There were 17 Omni Analytics outages since October 20, 2025 totaling 55h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.omniapp.co

Notice October 5, 2026

Response slowness from OpenAI models

Detected by Pingoru
Oct 05, 2026, 04:59 PM UTC
Resolved
Oct 05, 2026, 08:38 PM UTC
Duration
3h 38m
Timeline · 3 updates
  1. investigating Oct 05, 2026, 04:59 PM UTC

    We are currently investigating reports of intermittent delayed responses from OpenAI models in Omni. Our model provider AWS Bedrock is reporting increased error rates on OpenAI models at this time. We'll provide more information as soon as we have an update.

  2. identified Oct 05, 2026, 05:57 PM UTC

    Our model provider, AWS Bedrock, is currently reporting higher error rates for OpenAI models. Some AI requests may fail or stop partway through. We're monitoring and will update you when the issue is resolved on the provider's end.

  3. resolved Oct 05, 2026, 08:38 PM UTC

    Our model provider, AWS Bedrock, has reported the incident as resolved. Our testing confirms that OpenAI models are available again and AI requests are completing normally.

Read the full incident report →

Notice September 9, 2026

Support outage

Detected by Pingoru
Sep 09, 2026, 11:14 PM UTC
Resolved
Sep 09, 2026, 11:29 PM UTC
Duration
14m
Affected: EastUsaIrelandAustraliaCanadaIndiaAZEastUS2AZUKAZAustraliaAZCanadaAZUAEAZSEAsia
Timeline · 2 updates
  1. identified Sep 09, 2026, 11:14 PM UTC

    Our third-party support messaging service is experiencing an outage. Messages are currently delayed and response times may be longer than usual. For urgent requests, please email [email protected].

  2. resolved Sep 09, 2026, 11:29 PM UTC

    Our third-party support messaging service has resolved the issues causing their outage. Support messages are working normally.

Read the full incident report →

Critical August 27, 2026

Server Timeout Errors

Detected by Pingoru
Aug 27, 2026, 02:52 PM UTC
Resolved
Aug 27, 2026, 03:47 PM UTC
Duration
55m
Affected: Ireland
Timeline · 4 updates
  1. investigating Aug 27, 2026, 02:52 PM UTC

    We are aware of server timeout errors causing 500 errors on EU instances and are investigating

  2. monitoring Aug 27, 2026, 02:59 PM UTC

    One of our model services spiked and we are begging to see it recover.

  3. monitoring Aug 27, 2026, 03:36 PM UTC

    This incident has been resolved.

  4. resolved Aug 27, 2026, 03:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 17, 2026

Slow UI navigation

Detected by Pingoru
Aug 17, 2026, 05:31 PM UTC
Resolved
Aug 17, 2026, 08:46 PM UTC
Duration
3h 14m
Affected: EastUsa
Timeline · 3 updates
  1. investigating Aug 17, 2026, 05:31 PM UTC

    We have received reports of slowness navigating in Omni, we are currently investigating

  2. monitoring Aug 17, 2026, 05:42 PM UTC

    We've deployed additional infra to handle the increased load that was causing performance degradation. While performance should be mostly recovered, we are investigating the root cause of the performance spike.

  3. resolved Aug 17, 2026, 08:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 15, 2026

Degraded performance due to DOS attack

Detected by Pingoru
Jun 15, 2026, 01:30 PM UTC
Resolved
Jun 15, 2026, 01:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 17, 2026, 05:21 PM UTC

    On June 15th, at approximately 18:19 PDT our monitoring alerted elevated load balancer response times due to a spike in traffic that we quickly identified as a DOS attack attempt. We implemented a firewall rule to block the attack 8 minutes later with response times returning to normal for most customers over the next 5 to 10 minutes. We aim to provide notice of significant disruptions lasting more than 10 minutes and are retroactively posting this to meet that goal.

Read the full incident report →

Notice May 27, 2026

Slack Integration — Degraded Performance

Detected by Pingoru
May 27, 2026, 11:12 PM UTC
Resolved
May 28, 2026, 06:07 AM UTC
Duration
6h 55m
Affected: EastUsaIrelandAustraliaCanadaIndiaAZEastUS2
Timeline · 2 updates
  1. investigating May 27, 2026, 11:12 PM UTC

    We're aware of an active incident on Slack's end affecting Slack-based functionality in Omni. You may experience degraded performance with: - Scheduled deliveries via Slack - AI Slackbot interactions - Omni Support via Slack channels Omni's core infrastructure is fully operational. We're monitoring Slack's status page and will update this incident as it affects Omni functionality. If you need to report an urgent issue please email us at [email protected].

  2. resolved May 28, 2026, 06:07 AM UTC

    Slack is reporting: "Slack services have largely returned to normal operational levels. Messaging, Workflows, Apps, Integrations, APIs, and Connections have all been restored." We are now marking this resolved regarding Omni integrations with slack.

Read the full incident report →

Minor May 14, 2026

403 errors connecting to MCP clients

Detected by Pingoru
May 14, 2026, 09:32 AM UTC
Resolved
May 14, 2026, 12:46 PM UTC
Duration
3h 14m
Affected: EastUsaIreland
Timeline · 3 updates
  1. investigating May 14, 2026, 09:32 AM UTC

    We are currently investigating issues with users seeing 403 errors connecting to MCP clients

  2. monitoring May 14, 2026, 10:15 AM UTC

    We have identified the source of the issue, are implementing a patch and monitoring results

  3. resolved May 14, 2026, 12:46 PM UTC

    The fix has fully deployed now seeing service return to normal What happened: A change we shipped to the MCP OAuth flow yesterday introduced a regression in how authentication tokens were handled by MCP tool calls. The OAuth handshake itself succeeded, so connecting to the MCP server worked, but invoking specific tools (like listing models or running queries) returned a “403 Invalid bearer token” error. Who this affected: Customers using MCP integrations that connect through callbacks.omniapp.co (Claude, ChatGPT, etc). Direct connections from CLI clients are not affected.

Read the full incident report →

Major May 7, 2026

Pages returning `Application DB Error`

Detected by Pingoru
May 07, 2026, 01:44 AM UTC
Resolved
May 07, 2026, 03:11 AM UTC
Duration
1h 26m
Affected: EastUsaIreland
Timeline · 5 updates
  1. investigating May 07, 2026, 01:44 AM UTC

    We are currently investigating this issue.

  2. investigating May 07, 2026, 01:51 AM UTC

    A mitigation has been put in place and systems are showing stable. Users reporting this issue have confirmed normal function is returned at this time. We are continuing to investigate.

  3. identified May 07, 2026, 02:19 AM UTC

    We identified the source of the issue and are implementing a fix.

  4. monitoring May 07, 2026, 02:39 AM UTC

    A fix has been implemented. We are continuing to monitor for any unexpected behavior.

  5. resolved May 07, 2026, 03:11 AM UTC

    A scheduled update to an internal database table resulted in full page errors. A fix was put implemented to complete the update safely and the team is taking steps to ensure future updates do not cause errors.

Read the full incident report →

Notice April 17, 2026

DNS Resolution Issues for Some Users caused by their ISP

Detected by Pingoru
Apr 17, 2026, 04:51 PM UTC
Resolved
Apr 17, 2026, 08:36 PM UTC
Duration
3h 44m
Affected: EastUsa
Timeline · 4 updates
  1. investigating Apr 17, 2026, 04:51 PM UTC

    We are aware that some users are experiencing difficulty accessing their Omni instance. Omni and our DNS chain is healthy at this time. This appears to be related to a DNS resolution issue affecting certain ISPs on the user end. Users who can change their ISP have reported the issue resolved.

  2. identified Apr 17, 2026, 04:51 PM UTC

    This issue has been diagnosed and is not caused by Omni or the infrastructure we use.

  3. identified Apr 17, 2026, 04:53 PM UTC

    We will leave this incident up for some time to help users understand the source of their access issue.

  4. resolved Apr 17, 2026, 08:36 PM UTC

    The primary DNS provider reporting an issue has marked their incident resolved. We have not had any recent reports from Omni users.

Read the full incident report →

Critical February 25, 2026

Slowness detected in Omni

Detected by Pingoru
Feb 25, 2026, 06:44 PM UTC
Resolved
Feb 25, 2026, 07:22 PM UTC
Duration
38m
Affected: EastUsaIreland
Timeline · 6 updates
  1. investigating Feb 25, 2026, 06:44 PM UTC

    Our monitoring picked up slowness in the Omni App with error messages in some cases. We are investigating and working on mitigation.

  2. investigating Feb 25, 2026, 06:48 PM UTC

    We have identified the cause of the issue and are in the process of reverting the change.

  3. identified Feb 25, 2026, 06:58 PM UTC

    The team identified a recent change that caused performance degradation. We have rolled back to a previous deployment and are seeing recovery.

  4. identified Feb 25, 2026, 07:02 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Feb 25, 2026, 07:10 PM UTC

    The application is back online, and our monitoring shows performance metrics have returned to normal levels. We are continuing to monitor the situation.

  6. resolved Feb 25, 2026, 07:22 PM UTC

    The incident has been resolved, and all systems are back to operational status. We apologize for the disruption and are conducting a review to prevent the issue from happening again.

Read the full incident report →

Minor February 24, 2026

Slowness detected in Omni Application

Detected by Pingoru
Feb 24, 2026, 04:31 PM UTC
Resolved
Feb 24, 2026, 09:22 PM UTC
Duration
4h 50m
Affected: EastUsa
Timeline · 5 updates
  1. investigating Feb 24, 2026, 04:31 PM UTC

    We detected latency in our infrastructure and are in the process of mitigating. You may see full page errors as we adjust resources.

  2. investigating Feb 24, 2026, 05:09 PM UTC

    The system is currently behaving normally. Our team has identified possible causes of the slowness. We will continue to monitor and identify root cause fixes.

  3. monitoring Feb 24, 2026, 05:44 PM UTC

    All systems are normal. The team is continuing to monitor and is working to identify root cause fixes.

  4. monitoring Feb 24, 2026, 06:14 PM UTC

    The system continues to be stable. The team has identified the issue and is implementing a fix to prevent the issue from recurring.

  5. resolved Feb 24, 2026, 09:22 PM UTC

    This incident has been resolved. The team has made changes to prevent the issue from happening again, and our monitoring shows healthy operations for the last 4 hours.

Read the full incident report →

Notice February 18, 2026

Error loading pages

Detected by Pingoru
Feb 18, 2026, 07:55 PM UTC
Resolved
Feb 19, 2026, 12:39 AM UTC
Duration
4h 43m
Affected: EastUsa
Timeline · 2 updates
  1. monitoring Feb 18, 2026, 07:55 PM UTC

    A sudden spike in usage strained our system, and then a routine update added more pressure right after. We've fixed how we handle these situations so they won't pile up like this again. Our system now has plenty of capacity, and we're improving how it automatically adjusts to growth. We apologize for the delay in updating our status as we worked to determine if the original issue resurfaced or a new issue was present.

  2. resolved Feb 19, 2026, 12:39 AM UTC

    We've traced this incident to a configuration change on our end. We've reverted that change and we'll continue to monitor through future scaling events.

Read the full incident report →

Major February 18, 2026

Error loading pages in Omni - Something went wrong 500:Error

Detected by Pingoru
Feb 18, 2026, 03:05 PM UTC
Resolved
Feb 18, 2026, 06:06 PM UTC
Duration
3h 1m
Affected: EastUsa
Timeline · 7 updates
  1. investigating Feb 18, 2026, 03:05 PM UTC

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

  2. investigating Feb 18, 2026, 03:08 PM UTC

    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.

  3. monitoring Feb 18, 2026, 03:21 PM UTC

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

  4. investigating Feb 18, 2026, 04:20 PM UTC

    We are seeing increased application errors and are actively investigating.

  5. identified Feb 18, 2026, 05:32 PM UTC

    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.

  6. monitoring Feb 18, 2026, 05:42 PM UTC

    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.

  7. resolved Feb 18, 2026, 06:06 PM UTC

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

Read the full incident report →

Minor December 15, 2025

Partial Dashboard Loading Issues

Detected by Pingoru
Dec 15, 2025, 08:12 PM UTC
Resolved
Dec 15, 2025, 09:31 PM UTC
Duration
1h 19m
Affected: EastUsaIrelandAustraliaCanada
Timeline · 6 updates
  1. investigating Dec 15, 2025, 08:12 PM UTC

    We are currently investigating reports that some users are encountering "Internal Server Error" (500) when attempting to load certain dashboards. Our engineering team is actively investigating the root cause and is initiating a rollback of the recent deployment. We apologize for the disruption and will provide an update shortly.

  2. investigating Dec 15, 2025, 08:23 PM UTC

    We are continuing to investigate this issue.

  3. investigating Dec 15, 2025, 08:29 PM UTC

    We are continuing to investigate this issue.

  4. identified Dec 15, 2025, 08:38 PM UTC

    The team has identified the cause of the issue as being related to timeframes in drill fields. A fix is in progress.

  5. monitoring Dec 15, 2025, 08:58 PM UTC

    A fix has been released, and previously erroring dashboards are now loading successfully. We are continuing to monitor the incident to make sure there are no remaining issues for our users.

  6. resolved Dec 15, 2025, 09:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 4, 2025

Slowness in Omni detected

Detected by Pingoru
Dec 04, 2025, 09:15 AM UTC
Resolved
Dec 04, 2025, 05:12 PM UTC
Duration
7h 57m
Affected: Ireland
Timeline · 7 updates
  1. investigating Dec 04, 2025, 09:15 AM UTC

    We are aware of an internal error affecting access to Omni and are currently investigating

  2. investigating Dec 04, 2025, 09:34 AM UTC

    We are continuing to investigate the root cause of the issue

  3. monitoring Dec 04, 2025, 09:40 AM UTC

    A fix has been implemented and we're monitoring the results

  4. monitoring Dec 04, 2025, 10:29 AM UTC

    We are still monitoring the results of the fix. Requests to our internal CPU continue to be high and we are working on bringing it down

  5. monitoring Dec 04, 2025, 11:51 AM UTC

    We have mitigated the issues for now and the app has stabilised with some continued slowness still expected. We are continuing to look into the root cause to identify a permanent fix.

  6. monitoring Dec 04, 2025, 01:47 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Dec 04, 2025, 05:12 PM UTC

    This incident is now resolved. In certain configurations combined with a very large number of model extensions it was possible to issue a query to the internal database that exhausted resources. Our mitigation is stable and a permanent fix is in development.

Read the full incident report →

Major October 20, 2025

Query Execution Delays

Detected by Pingoru
Oct 20, 2025, 02:20 PM UTC
Resolved
Oct 21, 2025, 12:18 AM UTC
Duration
9h 58m
Affected: EastUsa
Timeline · 6 updates
  1. identified Oct 20, 2025, 02:20 PM UTC

    We are experiencing delays executing queries in Omni's US environment due to infrastructure issues with our cloud service provider.

  2. identified Oct 20, 2025, 02:23 PM UTC

    Query execution is backlogged until our cloud service provider's infrastructure allows us to provision more capacity, queries are executed in the order they are received, rerunning a query will not result in faster execution.

  3. identified Oct 20, 2025, 05:17 PM UTC

    No change from last status update. We continue to monitor closely and will scale up resources as soon as our cloud provider allows. Query execution is still backlogged until our cloud service provider's infrastructure allows us to provision more capacity, queries are executed in the order they are received, rerunning a query will not result in faster execution.

  4. identified Oct 20, 2025, 07:47 PM UTC

    We have been able to add some new resources to our infrastructure. Monitoring shows some improvement may be experienced in query processing. We are continuing to monitor and attempt to return to a fully stable service as soon as is allowed by our cloud provider's state of service.

  5. monitoring Oct 20, 2025, 09:11 PM UTC

    Our monitoring has been showing stable for the last hour despite our cloud provider maintaining degraded service status. We are expecting Omni services to be performing as expected. We will continue to monitor until our cloud provider reports all systems are stable.

  6. resolved Oct 21, 2025, 12:18 AM UTC

    Our monitoring has not shown any signs of lingering issues in the hour following our cloud providers marking of their incident as closed. We are considering this incident resolved.

Read the full incident report →