Omni Analytics Outage History

Omni Analytics is up right now

There were 5 Omni Analytics outages since February 18, 2026 totaling 16h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.omniapp.co

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 →

Looking to track Omni Analytics downtime and outages?

Pingoru polls Omni Analytics's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Omni Analytics reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Omni Analytics alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Omni Analytics for free

5 free monitors · No credit card required