Duration: 2 hours and 37 minutes

Affected Components: Dashboard, Composio Connect MCP, Composio CLI

Jul 16, 08:08:00 GMT+0
Investigating - We are currently investigating this incident..

Jul 16, 10:12:53 GMT+0
Monitoring - One of our auth provider had an outage and we got affected. The provider API calls are working and users are able to login now. We are monitoring the situation..

Jul 16, 10:45:00 GMT+0
Resolved - This incident has been resolved. We're monitoring the third party (WorkOs) status for any new updates here: <https://status.workos.com>.

Duration: 13 hours and 7 minutes

Affected Components: Triggers V2, Triggers V1

Jul 2, 04:48:00 GMT+0
Investigating - We're investigating reports that the GMAIL\_NEW\_GMAIL\_MESSAGE trigger has stopped delivering webhooks for a subset of accounts..

Jul 2, 17:40:00 GMT+0
Identified - We've identified the cause. A fix we reverted yesterday was unintentionally re-applied to production during a routine code sync, which re-introduced the same regression in our new-email polling filter. Impact is limited to GMAIL\_NEW\_GMAIL\_MESSAGE triggers configured without an explicit Gmail label. Less than 2% of overall GMAIL\_NEW\_GMAIL\_MESSAGE triggers are affected. We are rolling back the change now..

Jul 2, 17:52:00 GMT+0
Monitoring - We've reverted the change and webhook delivery has resumed. We're actively monitoring to confirm full recovery..

Jul 2, 17:55:00 GMT+0
Resolved - This incident has been resolved. Root cause: a change we had already reverted was re-introduced by an automated sync, re-causing yesterday's regression in the new-email polling logic. We're adding checks to prevent recurrence, and we're sorry for the disruption..

Duration: 3 hours and 15 minutes

Affected Components: Triggers V2, Triggers V1

Jul 1, 17:00:00 GMT+0
Identified - We have identified that the issue is scoped to GMAIL\_NEW\_GMAIL\_MESSAGE trigger and is affecting a very limited set of customers - 2% of GMAIL\_NEW\_GMAIL\_MESSAGE trigger instances..

Jul 1, 14:15:00 GMT+0
Investigating - We are currently investigating this incident..

Jul 1, 17:15:00 GMT+0
Monitoring - This incident has been resolved. It was a regression in the filtering query we use for polling new emails. We have reverted the change and actively monitoring it..

Jul 1, 17:29:58 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 24 minutes

Affected Components: COMPOSIO_SEARCH

Jun 27, 10:40:00 GMT+0
Investigating - We are currently investigating this incident..

Jun 29, 17:25:00 GMT+0
Resolved - Hosted web search requests failed due to a capacity limit with the upstream search provider. Capacity has been restored and we have verified full recovery. No action is needed on your end..

Duration: 41 minutes

Affected Components: Tool Execution

Jun 19, 11:04:00 GMT+0
Investigating - We are experiencing elevated error rates for the following toolkits: COMPOSIO\_SEARCH, YELP, INSTACART, TAVILY, GEMINI, SEAT\_GEEK , BROWSER\_TOOL and SERPAPI.

Jun 19, 11:10:00 GMT+0
Identified - We've narrowed down the impact to only the following toolkits and only versions strictly before `20260618_00` . Impacted toolkits: `COMPOSIO_SEARCH` `YELP` `INSTACART` `TAVILY` `GEMINI` `SEAT_GEEK` `BROWSER_TOOL` `SERPAPI` . Customers using `version=latest` remain unaffected. The root cause has been identified and the fix is rolling out..

Jun 19, 11:45:00 GMT+0
Resolved - This incident has been resolved. Tool executions across the impacted toolkits across all versions are now working normally..

Duration: 18 minutes

Affected Components: MCP Servers, Sandbox, v3 API, Composio Connect MCP, Proxy, Tool Search, Tool Execution, Connections

Jun 15, 21:30:00 GMT+0
Investigating - We are currently investigating this incident..

Jun 15, 21:48:00 GMT+0
Resolved - This incident has been resolved..

Duration: 4 hours

Affected Components: MCP Servers

Jun 11, 11:00:00 GMT+0
Investigating - We are investigating elevated errors on the MCP Servers endpoint (backend.composio.dev/v3/mcp). Some requests may fail. Sessions (Tool Router) and the rest of the v3 API are not affected. We will share an update shortly..

Jun 11, 15:00:00 GMT+0
Resolved - This incident has been resolved..

Duration: 7 hours and 20 minutes

Affected Components: Linear Auth

Jun 10, 09:42:00 GMT+0
Investigating - We're seeing elevated failures with Linear Auth Refresh for Composio Managed Connections. Some tool calls on existing Linear connections may fail. We've traced this to rate-limiting on Linear's API and are following up with the Linear team. Other integrations are unaffected - we'll post updates here..

Jun 10, 19:19:00 GMT+0
Resolved - This incident has been resolved. Auth refresh for Linear was being rate limited by Linear, it was resolved after increasing the refresh window. End users who have multiple (more than 3-4) Linear Accounts connected with their agents may still see auth refresh failures. .

Duration: 28 minutes

Affected Components: v3 API

Jun 9, 14:04:00 GMT+0
Identified - Seeing highly elevated API rates for a small subset of accounts.

Jun 9, 14:32:00 GMT+0
Resolved - This incident has been resolved. The issue was caused due to a mistimed coordinated deployment. Approximately 2% of all incoming requests were impacted..

Affected Components: Sandbox, Triggers V2, v3 API, Triggers V1, Proxy, Tool Search, Tool Execution

May 26, 08:00:00 GMT+0
Resolved - We have identified the issue..

May 26, 08:15:00 GMT+0
Resolved - This incident has been resolved..

Duration: 8 hours and 30 minutes

Affected Components: Sandbox, v3 API, Proxy, Tool Search, Tool Execution

May 26, 01:00:00 GMT+0
Investigating - We've noticed Vercel's firewall has been blocking many tool execution requests and other requests to the backend..

May 26, 09:30:09 GMT+0
Resolved - We have temporarily eased its restrictions. The Cloudflare WAF remains in place. If you receive a 403 with a request id resembling something like "cle:..." or some other 3 letter region prefix please try again or reach out to us. This incident has been resolved..

Duration: 5 days, 18 hours and 10 minutes

Affected Components: Sandbox, Triggers V2, v3 API, Composio Connect MCP, Composio CLI, Triggers V1, Proxy, Connections

May 26, 01:27:32 GMT+0
Resolved - This incident has been resolved..

May 25, 23:09:22 GMT+0
Identified - Ability to create new connections was down.

Duration: 15 hours and 21 minutes

Affected Components: Dashboard

May 24, 18:30:00 GMT+0
Investigating - We are currently investigating this incident..

May 25, 07:12:32 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 25, 09:51:21 GMT+0
Resolved - This incident has been resolved..

Duration: 1 day and 8 hours

Affected Components: Composio CLI

May 24, 17:30:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 26, 01:30:00 GMT+0
Resolved - CLI auth was broken and all existing CLI auth was revoked hence functionally bricking CLI.

Duration: 2 days and 20 hours

Affected Components: Composio Connect MCP

May 24, 02:30:00 GMT+0
Investigating - We are currently investigating this incident..

May 26, 22:30:00 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 27 minutes

Affected Components: Sandbox, v3 API, Proxy, Tool Search, Tool Execution, Connections

May 23, 11:05:40 GMT+0
Resolved - This incident has been resolved..

May 23, 09:38:27 GMT+0
Investigating - Ability to create new connections was down.

Duration: 5 hours and 43 minutes

Affected Components: Triggers V2, Triggers V1

May 22, 06:40:00 GMT+0
Identified - We've identified the root cause as a fall out of our mitigation towards the ongoing security incident. We had rotated internal secrets across multiple internal services but due to a misconfiguration in the delivery service, the inter-service communication between the trigger & delivery service is severed. We are working on restoring this ASAP..

May 22, 07:08:00 GMT+0
Monitoring - We have implemented the configuration fix and monitoring.

May 22, 07:13:13 GMT+0
Resolved - This incident has been resolved. We're seeing full recovery on delivery volumes..

May 22, 01:30:00 GMT+0
Investigating - We are aware about an ongoing incident affecting ALL webhook delivery from Composio platforms to customers. No webhooks/triggers are currently being delivered to customers..

Duration: 2 days and 34 minutes

May 21, 18:59:26 GMT+0
Identified - Learn more about here <https://composio.dev/blog/composio-may-2026-security-incident>.

May 25, 21:00:00 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 44 minutes

Affected Components: Github Auth

May 21, 17:58:19 GMT+0
Investigating - We are currently investigating this incident..

May 21, 18:01:51 GMT+0
Investigating - We are currently investigating this incident..

May 21, 19:42:07 GMT+0
Resolved - This incident has been resolved..

Duration: 32 minutes

Affected Components: Proxy, Tool Search, Sandbox, Triggers V2, Triggers V1, v3 API, Google Auth, Dashboard, Tool Execution, Twitter Auth

May 21, 12:19:00 GMT+0
Investigating - We are currently investigating this incident..

May 21, 12:33:00 GMT+0
Resolved - Fully resolved. Will shared more updates soon but was caused a progressive rollout causing failures in about 300 connected account decryptions causing both connected account list and tool execution failures.

Duration: 2 hours and 45 minutes

Affected Components: v3 API, Tool Execution

May 21, 10:35:00 GMT+0
Investigating - We’re investigating an issue affecting file upload and download actions across toolkits. Some requests may fail, time out, or return incomplete results. We’re actively working on a fix and will share updates soon..

May 21, 12:35:01 GMT+0
Investigating - We're investigating an issue file upload/download actions across certain toolkits. Some file operations may time out or return incomplete results. Other functionality remains largely unaffected. Our team is actively working on a fix and we'll share updates soon..

May 21, 13:19:48 GMT+0
Resolved - This incident has been resolved..

Duration: 9 minutes

Affected Components: Proxy, Tool Search, Sandbox, v3 API, Tool Execution

May 21, 10:27:30 GMT+0
Investigating - We are currently investigating this incident..

May 21, 10:36:40 GMT+0
Resolved - This incident has been resolved..

Duration: 11 hours and 18 minutes

Affected Components: Tool Search

May 18, 20:53:00 GMT+0
Monitoring - One of our inference providers had degraded latencies today. We noticed degraded performance in search execution across the few hours. It affected a subset of users depending on inference routing patterns. A fix and been pushed and we are monitoring the situation..

May 18, 19:00:00 GMT+0
Investigating - Investing an issue with search performance being intermittently degraded.

May 19, 06:18:14 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 16 minutes

Affected Components: Triggers V2

May 14, 14:04:00 GMT+0
Investigating - We are currently investigating an incident impacting slack triggers on the platform.

May 14, 14:54:58 GMT+0
Monitoring - We have confirmed that our systems are operational, but we are experiencing issues on slack events ingress due to an ongoing slack outage: <https://slack-status.com/2026-05/fe557ca05fdb64fa>. We are closely monitoring the situation and will update as things progress on slack's end..

May 14, 15:06:00 GMT+0
Monitoring - Slack's systems are still degraded (<https://slack-status.com/2026-05/fe557ca05fdb64fa>). But, we are seeing some early signs of recovery on slack's end, the ingress volume is still unstable and fluctuating rapidly. Webhook deliveries may be delayed or missed. We are closely monitoring the situation..

May 14, 15:20:00 GMT+0
Resolved - Slack triggers should now be back up again! We're now seeing near full recovery for slack triggers as slack systems come back online: <https://slack-status.com/2026-05/fe557ca05fdb64fa>.

Duration: 12 minutes

Affected Components: Triggers V2, Triggers V1, v3 API, , Dashboard, Tool Execution, Sessions (Tool Router) →

May 8, 10:51:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 8, 11:01:10 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 8, 11:02:52 GMT+0
Resolved - This incident has been resolved..