Is Omni Analytics down?

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.

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].

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.

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

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

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.

We are currently investigating this issue.

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.

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

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

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.