AppOmni Outage History

AppOmni is up right now

AppOmni had 13 outages in the last 2 years totaling 99h 50m of downtime — averaging 0.5 incidents per month.

There were 13 AppOmni outages since September 10, 2025 totaling 99h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.appomni.com

Minor August 6, 2026

Delayed Detection Alerts

Detected by Pingoru
Aug 06, 2026, 03:17 PM UTC
Resolved
Aug 06, 2026, 09:35 PM UTC
Duration
6h 17m
Affected: Threat Detection
Timeline · 4 updates
  1. investigating Aug 06, 2026, 03:17 PM UTC

    Threat detection alerts in the Australia region are being generated later than usual; event collection, retention, search, and posture monitoring are unaffected.

  2. identified Aug 06, 2026, 05:38 PM UTC

    The issue with detection alert delays in the Australia region has been identified and a fix is being implemented.

  3. monitoring Aug 06, 2026, 07:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 06, 2026, 09:35 PM UTC

    Threat detection alerting in the Australia region returned to normal processing times. Some alerts from the affected period will continue to arrive backdated over the next few hours.

Read the full incident report →

Minor July 13, 2026

Detection Collection and Alerting Delays

Detected by Pingoru
Jul 13, 2026, 01:24 PM UTC
Resolved
Jul 13, 2026, 11:36 PM UTC
Duration
10h 12m
Affected: Threat Detection
Timeline · 4 updates
  1. identified Jul 13, 2026, 01:24 PM UTC

    We are investigating an issue with delayed event collection and alerting for some US-based customers.

  2. monitoring Jul 13, 2026, 01:33 PM UTC

    A fix has been implemented for an issue that delayed data collection and threat-detection processing for some US customers. We are now monitoring as the affected data catches up.

  3. monitoring Jul 13, 2026, 10:14 PM UTC

    Recovery is progressing. Data collection has returned to normal, and the remaining delayed threat-detection data is catching up. We expect delays to fully clear overnight and will confirm once complete.

  4. resolved Jul 13, 2026, 11:36 PM UTC

    Data collection and threat detection have recovered. We'll continue to monitor closely as event delivery finishes catching up.

Read the full incident report →

Minor June 15, 2026

Performance Degradation of Policy Scans

Detected by Pingoru
Jun 15, 2026, 03:13 PM UTC
Resolved
Jun 16, 2026, 12:32 PM UTC
Duration
21h 18m
Affected: Policy Scans
Timeline · 3 updates
  1. investigating Jun 15, 2026, 03:13 PM UTC

    We are currently investigating the issue

  2. investigating Jun 16, 2026, 12:31 PM UTC

    All Policy Scans are operational. We will continue to monitor closely.

  3. resolved Jun 16, 2026, 12:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 4, 2026

Detection Event Collection Issues

Detected by Pingoru
Jun 04, 2026, 06:27 PM UTC
Resolved
Jun 05, 2026, 02:54 PM UTC
Duration
20h 27m
Affected: Threat Detection
Timeline · 3 updates
  1. investigating Jun 04, 2026, 06:27 PM UTC

    We are investigating an issue with event collection for some US-based customers.

  2. monitoring Jun 04, 2026, 08:05 PM UTC

    Event collection and processing have been restored and are operating at normal event volumes across the platform. We will continue monitoring collection to ensure stability.

  3. resolved Jun 05, 2026, 02:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 13, 2026

Degradation of AppOmni Console Performance

Detected by Pingoru
Mar 13, 2026, 01:05 PM UTC
Resolved
Mar 13, 2026, 02:19 PM UTC
Duration
1h 13m
Affected: AppOmni Console
Timeline · 2 updates
  1. investigating Mar 13, 2026, 01:05 PM UTC

    We are experiencing degradation of performance for US customers attempting to access the AppOmni console. We are currently investigating the issue.

  2. resolved Mar 13, 2026, 02:19 PM UTC

    The degradation of performance for US-based customers has been resolved. We will continue to actively monitor performance to ensure there are no regressions.

Read the full incident report →

Minor March 5, 2026

Detection Alert Delivery Delay

Detected by Pingoru
Mar 05, 2026, 05:40 PM UTC
Resolved
Mar 05, 2026, 06:54 PM UTC
Duration
1h 14m
Affected: Threat Detection
Timeline · 5 updates
  1. investigating Mar 05, 2026, 03:21 PM UTC

    We are currently investigating an issue where some customers may experience delays in receiving threat detection alerts.

  2. identified Mar 05, 2026, 03:48 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 05, 2026, 04:18 PM UTC

    A fix has been deployed and alert processing has stabilized. We will continue to monitor as the remaining backlog is processed.

  4. monitoring Mar 05, 2026, 05:40 PM UTC

    Detection alert delivery delays have been resolved. We will continue to monitor for any changes.

  5. resolved Mar 05, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Event Destination Delivery Delay

Detected by Pingoru
Mar 02, 2026, 09:03 PM UTC
Resolved
Mar 03, 2026, 12:13 AM UTC
Duration
3h 9m
Affected: Threat Detection
Timeline · 4 updates
  1. monitoring Mar 02, 2026, 09:03 PM UTC

    Some customers experienced delayed event delivery due to an edge case that created a backlog and reduced throughput. Mitigation has been implemented, processing capacity increased, and backlog recovery is underway.

  2. investigating Mar 02, 2026, 09:37 PM UTC

    We are investigating reports of delayed event delivery to configured destinations.

  3. monitoring Mar 02, 2026, 10:17 PM UTC

    Recovery is progressing and event delivery performance continues to improve. We are monitoring system stability as backlog processing completes.

  4. resolved Mar 03, 2026, 12:13 AM UTC

    Event delivery has returned to normal operating levels. This incident has been resolved.

Read the full incident report →

Minor February 20, 2026

Inaccurate number of finding occurrences

Detected by Pingoru
Feb 20, 2026, 06:02 PM UTC
Resolved
Feb 21, 2026, 12:56 AM UTC
Duration
6h 53m
Affected: Posture Findings
Timeline · 5 updates
  1. investigating Feb 20, 2026, 06:02 PM UTC

    We are currently investigating an issue where some open posture findings for some of the monitored services are being reported inaccurately. The Posture Findings is still operational. We will provide an update by end of business day

  2. identified Feb 20, 2026, 10:12 PM UTC

    The issue has been identified and fix is being implemented. More updates will be provided soon once the fix is ready to be deployed

  3. monitoring Feb 21, 2026, 12:29 AM UTC

    The root cause has been identified and a fix has now been rolled out.

  4. monitoring Feb 21, 2026, 12:30 AM UTC

    We are continuing to monitor for any further issues before marking the incident as resolved

  5. resolved Feb 21, 2026, 12:56 AM UTC

    This incident has now been resolved

Read the full incident report →

Notice January 5, 2026

Threat Detection Event Processing Delays

Detected by Pingoru
Jan 05, 2026, 05:36 PM UTC
Resolved
Dec 28, 2025, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 05, 2026, 05:36 PM UTC

    Customers experienced delayed Threat Detection alerts due to a processing disruption. All events were processed after recovery, no data was lost, and the issue has been resolved.

Read the full incident report →

Minor November 25, 2025

Networking issues with the API Documentation site

Detected by Pingoru
Nov 25, 2025, 07:38 PM UTC
Resolved
Nov 26, 2025, 04:39 AM UTC
Duration
9h 1m
Affected: API Docs
Timeline · 3 updates
  1. investigating Nov 25, 2025, 07:38 PM UTC

    We are currently investigating an issue with our API Documentation site api.appomni.com There is no impact to the functioning of the APIs

  2. investigating Nov 25, 2025, 07:48 PM UTC

    We have contacted the 3rd party service that hosts our API Documentation to help resolve the issue

  3. resolved Nov 26, 2025, 04:39 AM UTC

    This incident has been resolved. api.appomni.con is back online. Thank you for your patience.

Read the full incident report →

Minor November 25, 2025

ServiceNow connection issues

Detected by Pingoru
Nov 25, 2025, 05:59 PM UTC
Resolved
Nov 25, 2025, 07:30 PM UTC
Duration
1h 31m
Affected: Monitored Services Data Sync
Timeline · 5 updates
  1. investigating Nov 25, 2025, 05:59 PM UTC

    We are currently investigating an issue related to some ServiceNow instances unable to connect to AppOmni

  2. investigating Nov 25, 2025, 05:59 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 25, 2025, 06:17 PM UTC

    The issue has been identified and we are in the process of determining a fix. The issue has been partially resolved but disconnects may happen again. We are closely monitoring the situation.

  4. monitoring Nov 25, 2025, 07:15 PM UTC

    Fix has been identified and deployed. The ServiceNow instances are now reconnected. We are currently monitoring the situation closely.

  5. resolved Nov 25, 2025, 07:30 PM UTC

    This incident has been resolved. We will continue to closely monitor.

Read the full incident report →

Notice September 11, 2025

Degraded Website and API performance

Detected by Pingoru
Sep 11, 2025, 06:00 PM UTC
Resolved
Sep 12, 2025, 12:30 PM UTC
Duration
18h 30m
Timeline · 1 update
  1. resolved Sep 12, 2025, 04:38 PM UTC

    Some customers may have experienced degraded performance across our website and API endpoints. Our team has identified and resolved the issue.

Read the full incident report →

Notice September 10, 2025

Delays in the processing of background tasks

Detected by Pingoru
Sep 10, 2025, 12:57 PM UTC
Resolved
Sep 10, 2025, 12:57 PM UTC
Duration
—
Affected: Monitored Services Data SyncPolicy ScansThreat DetectionInsights AssessmentsReport GenerationEmail Notifications
Timeline · 1 update
  1. resolved Sep 10, 2025, 12:57 PM UTC

    Some customers may have experienced degraded AppOmni console performance and some background tasks may have been delayed

Read the full incident report →