Is Omni Analytics down?
Last checked 7m agoNo incidents right now.
Omni Analytics is operational right now. Last checked 7m ago; the most recent incident resolved 17d ago.
Real-time Omni Analytics status, recent outages, and incident history — pulled directly from Omni Analytics's official status page at https://status.omniapp.co every 5 minutes. Pingoru tracks 6 Omni Analytics services and has captured 5 incidents in the last 90 days (99.07% uptime). Get email, Slack, Discord, or webhook alerts the moment Omni Analytics reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- EastUsaIrelandAustraliaCanadaIndiaAZEastUS2
Timeline · 2 updates
- 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].
- 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.
Latest: Slack is reporting: "Slack services have largely returned to normal operational levels. Messaging, Workflows, Apps, Integrations, APIs, and Connections have all been restored." We …
-
- EastUsaIreland
Timeline · 3 updates
- investigating · May 14, 2026, 09:32 AM UTC
We are currently investigating issues with users seeing 403 errors connecting to MCP clients
- monitoring · May 14, 2026, 10:15 AM UTC
We have identified the source of the issue, are implementing a patch and monitoring results
- 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.
Latest: 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 toke…
-
- EastUsaIreland
Timeline · 5 updates
- investigating · May 07, 2026, 01:44 AM UTC
We are currently investigating this issue.
- 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.
- identified · May 07, 2026, 02:19 AM UTC
We identified the source of the issue and are implementing a fix.
- monitoring · May 07, 2026, 02:39 AM UTC
A fix has been implemented. We are continuing to monitor for any unexpected behavior.
- 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.
Latest: 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…
-
- EastUsa
Timeline · 4 updates
- 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.
- identified · Apr 17, 2026, 04:51 PM UTC
This issue has been diagnosed and is not caused by Omni or the infrastructure we use.
- 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.
- 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.
Latest: The primary DNS provider reporting an issue has marked their incident resolved. We have not had any recent reports from Omni users.
-
- Started May 27, 2026, 11:12 PM UTC · Resolved May 28, 2026, 06:07 AM UTC · 6h 55m
- 403 errors connecting to MCP clients ResolvedStarted May 14, 2026, 09:32 AM UTC · Resolved May 14, 2026, 12:46 PM UTC · 3h 14m
- Started May 07, 2026, 01:44 AM UTC · Resolved May 07, 2026, 03:11 AM UTC · 1h 26m
- Started Apr 17, 2026, 04:51 PM UTC · Resolved Apr 17, 2026, 08:36 PM UTC · 3h 44m