Looking for an update now? Check the current status, or follow Omni Analytics for future changes.
97.1%of 35 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
28
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
One of our model services spiked and we are beginning to see it recover.
investigating
We are aware of server timeout errors causing 500 errors on EU instances and are investigating
Legacy Incident Archive
5 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Slow UI navigation
minorSource not attested
Last archived state: resolved
View archived record details
EastUsa
monitoring
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.
investigating
We have received reports of slowness navigating in Omni, we are currently investigating
May 2026
Slack Integration — Degraded Performance
Source not attested
Last archived state: resolved
View archived record details
investigating
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 support@omni.co.
403 errors connecting to MCP clients
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the source of the issue, are implementing a patch and monitoring results
investigating
We are currently investigating issues with users seeing 403 errors connecting to MCP clients
Pages returning `Application DB Error`
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented. We are continuing to monitor for any unexpected behavior.
identified
We identified the source of the issue and are implementing a fix.
investigating
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.
investigating
We are currently investigating this issue.
April 2026
DNS Resolution Issues for Some Users caused by their ISP
Source not attested
Last archived state: resolved
View archived record details
identified
We will leave this incident up for some time to help users understand the source of their access issue.
identified
This issue has been diagnosed and is not caused by Omni or the infrastructure we use.
investigating
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.
