Omni Analytics incident

403 errors connecting to MCP clients

Minor Resolved View vendor source →

Omni Analytics experienced a minor incident on May 14, 2026 affecting EastUsa and Ireland, lasting 3h 14m. The incident has been resolved; the full update timeline is below.

Started
May 14, 2026, 09:32 AM UTC
Resolved
May 14, 2026, 12:46 PM UTC
Duration
3h 14m
Detected by Pingoru
May 14, 2026, 09:32 AM UTC

Affected components

EastUsaIreland

Update timeline

  1. investigating May 14, 2026, 09:32 AM UTC

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

  2. monitoring May 14, 2026, 10:15 AM UTC

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

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