<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.composio.dev,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.composio.dev"/>
  <link rel="self" type="application/atom+xml" href="https://status.composio.dev/history.atom"/>
  <title>Composio Status - Incident history</title>
  <updated>2026-10-06T19:42:00.000+00:00</updated>
  <author>
    <name>Composio</name>
  </author>
  
<entry>
  <id>tag:status.composio.dev,2005:Incident/cmuxlzwoi00a81mry5wov5ly3</id>
  <published>2026-10-06T19:42:00.000+00:00</published>
  <updated>2026-10-06T19:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmuxlzwoi00a81mry5wov5ly3"/>
  <title>Elevated errors on Composio Connect MCP</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> Composio Connect MCP</p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>19:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating elevated error rates affecting Composio Connect MCP. Approximately 19% of users are receiving 502 errors on requests. Next update by 21:00 UTC..</p>
<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>03:40:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Composio Connect MCP has been fully restored as of 03:40 UTC on 7 October. Between 19:42 UTC on 6 October and 03:40 UTC, approximately 19% of users received 502 errors on requests due to infrastructure degradation. No customer data was affected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmuvm6vt606l21mjwr2aokusg</id>
  <published>2026-10-05T11:30:00.000+00:00</published>
  <updated>2026-10-05T11:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmuvm6vt606l21mjwr2aokusg"/>
  <title>Discord Bot toolkit is not available for tool executions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 6 hours</p>
    <p><strong>Affected Components:</strong> Discord Bot</p>
    <p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Discord Bot toolkit is temporarily unavailable while we make important design improvements. We&#039;re also evaluating whether we&#039;ll continue to support Composio-managed Discord bot connections. Discord Bot tool calls will return an error until the toolkit is back. We&#039;ll share an update soon..</p>
<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>17:29:55</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have retired all previous versions of DISCORDBOT toolkit and pushed a new version with the required fixes and design improvements. Proxy execute and some tools have been disabled for this toolkit. More details will be published on Changelog soon..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmurgng9a011014l6pv0qtrhv</id>
  <published>2026-10-02T20:07:00.000+00:00</published>
  <updated>2026-10-02T20:07:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmurgng9a011014l6pv0qtrhv"/>
  <title>Elevated errors in Instagram toolkit</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 34 minutes</p>
    <p><strong>Affected Components:</strong> INSTAGRAM</p>
    <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>20:07:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>20:40:45</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>21:40:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  All instagram accounts connected before August 3 got expired.   
We have fixed the issue in our refresh logic for instagram.  
For older accounts, user need to reauthenticate..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmu7k7wtk06lw0wrudzkbk8e3</id>
  <published>2026-09-18T22:58:24.437+00:00</published>
  <updated>2026-09-18T23:00:06.302+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmu7k7wtk06lw0wrudzkbk8e3"/>
  <title>Authentication related issues on dashboard and for you (CLI and MCP)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> Dashboard, Composio Connect MCP, Composio CLI</p>
    <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>23:00:06</var> GMT+0</small><br /><strong>Identified</strong> -
  One of our vendors, workos is facing elevated API failures &lt;https://status.workos.com/&gt;.</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>23:06:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>22:58:24</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmu56ait702uc13uikzdajbmu</id>
  <published>2026-09-17T06:40:00.000+00:00</published>
  <updated>2026-09-17T06:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmu56ait702uc13uikzdajbmu"/>
  <title>Elevated errors on platform APIs</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 minutes</p>
    <p><strong>Affected Components:</strong> MCP Servers, Sandbox, Triggers V2, v3 API, Dashboard, Composio Connect MCP, Composio CLI, Triggers V1, Tool Execution, Proxy, Tool Search, Connections</p>
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>06:40:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>06:56:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmtmmzhpd09021aqq06819cru</id>
  <published>2026-09-02T19:20:00.000+00:00</published>
  <updated>2026-09-02T19:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmtmmzhpd09021aqq06819cru"/>
  <title>Webhook Triggers Degraded</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 10 minutes</p>
    <p><strong>Affected Components:</strong> Triggers V2, Triggers V1</p>
    <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>19:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Webhook based triggers processing is degraded.

Polling based triggers continue to function as expected..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>20:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

Backlog of webhook payloads is cleared now..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>19:50:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have started processing our webhook based triggers and backlog is being cleared now.

There will still be some delay as the backlog gets flushed.

No impact on polling triggers as mentioned above..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmt744lhn1rzq0zmedz4bgfw3</id>
  <published>2026-08-24T10:00:00.000+00:00</published>
  <updated>2026-08-24T10:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmt744lhn1rzq0zmedz4bgfw3"/>
  <title>API Latencies are elevated</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 29 minutes</p>
    <p><strong>Affected Components:</strong> Triggers V2, v3 API, Triggers V1</p>
    <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>10:16:53</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>11:29:15</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

Our latency numbers are looking good and slack triggers continue to work now..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>11:00:44</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Slack triggers are turned off as part of remediation of platform latencies..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmt540sm319yu0kpbh0n74x9i</id>
  <published>2026-08-22T23:47:00.000+00:00</published>
  <updated>2026-08-22T23:47:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmt540sm319yu0kpbh0n74x9i"/>
  <title>Facing rate limits on Composio Managed Quickbooks App</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> Quickbooks</p>
    <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>23:47:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident. But, we recommend you moving your production workflows to your own OAuth apps. .</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>02:41:03</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>02:41:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Rate limits have been upgraded..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmrncjg7o00ka0kmohym0hkmm</id>
  <published>2026-07-16T08:08:00.000+00:00</published>
  <updated>2026-07-16T10:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmrncjg7o00ka0kmohym0hkmm"/>
  <title>Dashboard login issues and Composio For You Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> Dashboard, Composio Connect MCP, Composio CLI</p>
    <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>10:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.  
  
We&#039;re monitoring the third party (WorkOs) status for any new updates here: &lt;https://status.workos.com&gt;.</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>08:08:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>10:12:53</var> GMT+0</small><br /><strong>Monitoring</strong> -
  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..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmr4qdf3o00050zo468ukjkz7</id>
  <published>2026-07-02T04:48:00.000+00:00</published>
  <updated>2026-07-02T04:48:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmr4qdf3o00050zo468ukjkz7"/>
  <title>Issues with Gmail triggers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> Triggers V2, Triggers V1</p>
    <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>04:48:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re investigating reports that the GMAIL\_NEW\_GMAIL\_MESSAGE trigger has stopped delivering webhooks for a subset of accounts..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>17:40:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;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..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>17:52:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We&#039;ve reverted the change and webhook delivery has resumed. We&#039;re actively monitoring to confirm full recovery..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>17:55:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

Root cause: a change we had already reverted was re-introduced by an automated sync, re-causing yesterday&#039;s regression in the new-email polling logic. We&#039;re adding checks to prevent recurrence, and we&#039;re sorry for the disruption..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmr2cf3ub00em0lqox5c6l96x</id>
  <published>2026-07-01T14:15:00.000+00:00</published>
  <updated>2026-07-01T17:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmr2cf3ub00em0lqox5c6l96x"/>
  <title>Issues with Gmail triggers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> Triggers V2, Triggers V1</p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:15:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:29:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmqzi0x1i00830rnyh7fpjnh2</id>
  <published>2026-06-27T10:40:00.000+00:00</published>
  <updated>2026-06-27T10:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmqzi0x1i00830rnyh7fpjnh2"/>
  <title>Composio Web Search Tools are failing intermittently</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 24 minutes</p>
    <p><strong>Affected Components:</strong> COMPOSIO_SEARCH</p>
    <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>10:40:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>17:25:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  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..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmqkwdeac0edp2ikk3hx9kzag</id>
  <published>2026-06-19T11:04:00.000+00:00</published>
  <updated>2026-06-19T11:04:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmqkwdeac0edp2ikk3hx9kzag"/>
  <title>Tool execution degraded for the following toolkits (non-latest versions only)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> Tool Execution</p>
    <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>11:04:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are experiencing elevated error rates for the following toolkits: COMPOSIO\_SEARCH, YELP, INSTACART, TAVILY, GEMINI, SEAT\_GEEK , BROWSER\_TOOL and SERPAPI.</p>
<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>11:10:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;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..</p>
<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>11:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Tool executions across the impacted toolkits across all versions are now working normally..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmqfrexm90d5s2ik788efksz5</id>
  <published>2026-06-15T21:30:00.000+00:00</published>
  <updated>2026-06-15T21:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmqfrexm90d5s2ik788efksz5"/>
  <title>Elevated authentication errors on the API and SDK</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 minutes</p>
    <p><strong>Affected Components:</strong> MCP Servers, Sandbox, v3 API, Composio Connect MCP, Proxy, Tool Search, Tool Execution, Connections</p>
    <p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>21:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>21:48:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmq9nrvzw0171pdlz1fda2wh5</id>
  <published>2026-06-11T11:00:00.000+00:00</published>
  <updated>2026-06-11T11:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmq9nrvzw0171pdlz1fda2wh5"/>
  <title>MCP Servers endpoint returning errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> MCP Servers</p>
    <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmq80nb7708nrqtwgv413wfk3</id>
  <published>2026-06-10T09:42:00.000+00:00</published>
  <updated>2026-06-10T09:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmq80nb7708nrqtwgv413wfk3"/>
  <title>Degraded - Linear connection refresh </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> Linear Auth</p>
    <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>09:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re seeing elevated failures with Linear Auth Refresh for Composio Managed Connections. Some tool calls on existing Linear connections may fail.   
We&#039;ve traced this to rate-limiting on Linear&#039;s API and are following up with the Linear team. Other integrations are unaffected - we&#039;ll post updates here..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>19:19:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  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. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmq6s399k00rwpkk4wz6f6uf1</id>
  <published>2026-06-09T14:04:00.000+00:00</published>
  <updated>2026-06-09T14:04:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmq6s399k00rwpkk4wz6f6uf1"/>
  <title>Certain customers are experiencing highly elevated API error rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> v3 API</p>
    <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>14:04:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Seeing highly elevated API rates for a small subset of accounts.</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>14:32:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The issue was caused due to a mistimed coordinated deployment. Approximately 2% of all incoming requests were impacted..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpmd7t3z0amgnrlt5zyr50sa</id>
  <published>2026-05-26T08:00:00.000+00:00</published>
  <updated>2026-05-26T08:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpmd7t3z0amgnrlt5zyr50sa"/>
  <title>Issues with Composio APIs</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Sandbox, Triggers V2, v3 API, Triggers V1, Proxy, Tool Search, Tool Execution</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have identified the issue..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>08:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpmhcyqz0ps7p2mekehyk97a</id>
  <published>2026-05-26T01:00:00.000+00:00</published>
  <updated>2026-05-26T01:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpmhcyqz0ps7p2mekehyk97a"/>
  <title>Valid Requests Being Blocked By Vercel Firewall</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Sandbox, v3 API, Proxy, Tool Search, Tool Execution</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;ve noticed Vercel&#039;s firewall has been blocking many tool execution requests and other requests to the backend..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:30:09</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have temporarily eased its restrictions. The Cloudflare WAF remains in place. If you receive a 403 with a request id resembling something like &quot;cle:...&quot; or some other 3 letter region prefix please try again or reach out to us.  
This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpltj6us0ivkp2n0taui7p14</id>
  <published>2026-05-25T23:09:22.193+00:00</published>
  <updated>2026-05-26T01:27:32.180+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpltj6us0ivkp2n0taui7p14"/>
  <title>Issues with Composio Platform</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 18 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> Sandbox, Triggers V2, v3 API, Composio Connect MCP, Composio CLI, Triggers V1, Proxy, Connections</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>01:27:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>23:09:22</var> GMT+0</small><br /><strong>Identified</strong> -
  Ability to create new connections was down.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpkaxwcu007vpbmknq0c51dv</id>
  <published>2026-05-24T18:30:00.000+00:00</published>
  <updated>2026-05-24T18:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpkaxwcu007vpbmknq0c51dv"/>
  <title>Dashboard down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> Dashboard</p>
    <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>07:12:32</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>09:51:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpkax4n704thp2n0h1g58upe</id>
  <published>2026-05-24T17:30:00.000+00:00</published>
  <updated>2026-05-24T17:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpkax4n704thp2n0h1g58upe"/>
  <title>Issues with Composio CLI</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 8 hours</p>
    <p><strong>Affected Components:</strong> Composio CLI</p>
    <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>01:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  CLI auth was broken and all existing CLI auth was revoked hence functionally bricking CLI.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpkazjh604jjp2mem1swnpiq</id>
  <published>2026-05-24T02:30:00.000+00:00</published>
  <updated>2026-05-24T02:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpkazjh604jjp2mem1swnpiq"/>
  <title>Issues with MCP connection creation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 20 hours</p>
    <p><strong>Affected Components:</strong> Composio Connect MCP</p>
    <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>22:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpi5one00755pbhlf1tfqmhr</id>
  <published>2026-05-23T09:38:27.579+00:00</published>
  <updated>2026-05-23T11:05:40.991+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpi5one00755pbhlf1tfqmhr"/>
  <title>Composio Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 27 minutes</p>
    <p><strong>Affected Components:</strong> Sandbox, v3 API, Proxy, Tool Search, Tool Execution, Connections</p>
    <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>11:05:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>09:38:27</var> GMT+0</small><br /><strong>Investigating</strong> -
  Ability to create new connections was down.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.composio.dev,2005:Incident/cmpgk6vx700grpcn90phoc7rm</id>
  <published>2026-05-22T01:30:00.000+00:00</published>
  <updated>2026-05-22T06:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.composio.dev/incident/cmpgk6vx700grpcn90phoc7rm"/>
  <title>All outgoing webhook &amp; trigger deliveries are facing an outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 43 minutes</p>
    <p><strong>Affected Components:</strong> Triggers V2, Triggers V1</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>06:40:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;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 &amp; delivery service is severed. We are working on restoring this ASAP..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>07:08:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have implemented the configuration fix and monitoring.</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>07:13:13</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. We&#039;re seeing full recovery on delivery volumes..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>01:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>

        ]]>
  </content>
</entry>

</feed>