<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Composio Status - Incident history</title>
    <link>https://status.composio.dev</link>
    <description>Composio</description>
    <pubDate>Thu, 16 Jul 2026 08:08:00 +0000</pubDate>
    
<item>
  <title>Dashboard login issues and Composio For You Outage</title>
  <description>
    Type: Incident
    Duration: 2 hours and 37 minutes

    Affected Components: Dashboard, Composio Connect MCP, Composio CLI
    Jul 16, 10:45:00 GMT+0 - Resolved - 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; 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:08:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:12:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 16 Jul 2026 08:08:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmrncjg7o00ka0kmohym0hkmm</link>
  <guid>https://status.composio.dev/incident/cmrncjg7o00ka0kmohym0hkmm</guid>
</item>

<item>
  <title>Issues with Gmail triggers</title>
  <description>
    Type: Incident
    Duration: 13 hours and 7 minutes

    Affected Components: Triggers V2, Triggers V1
    Jul 2, 04:48:00 GMT+0 - Investigating - We&#039;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&#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. Jul 2, 17:52:00 GMT+0 - Monitoring - We&#039;ve reverted the change and webhook delivery has resumed. We&#039;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&#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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:48:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;re investigating reports that the GMAIL\_NEW\_GMAIL\_MESSAGE trigger has stopped delivering webhooks for a subset of accounts..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:52:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We&#039;ve reverted the change and webhook delivery has resumed. We&#039;re actively monitoring to confirm full recovery..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 2 Jul 2026 04:48:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmr4qdf3o00050zo468ukjkz7</link>
  <guid>https://status.composio.dev/incident/cmr4qdf3o00050zo468ukjkz7</guid>
</item>

<item>
  <title>Issues with Gmail triggers</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:29:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 1 Jul 2026 14:15:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmr2cf3ub00em0lqox5c6l96x</link>
  <guid>https://status.composio.dev/incident/cmr2cf3ub00em0lqox5c6l96x</guid>
</item>

<item>
  <title>Composio Web Search Tools are failing intermittently</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 24 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 27 Jun 2026 10:40:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmqzi0x1i00830rnyh7fpjnh2</link>
  <guid>https://status.composio.dev/incident/cmqzi0x1i00830rnyh7fpjnh2</guid>
</item>

<item>
  <title>Tool execution degraded for the following toolkits (non-latest versions only)</title>
  <description>
    Type: Incident
    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&#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. 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:04:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are experiencing elevated error rates for the following toolkits: COMPOSIO\_SEARCH, YELP, INSTACART, TAVILY, GEMINI, SEAT\_GEEK , BROWSER\_TOOL and SERPAPI.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Tool executions across the impacted toolkits across all versions are now working normally..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 19 Jun 2026 11:04:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmqkwdeac0edp2ikk3hx9kzag</link>
  <guid>https://status.composio.dev/incident/cmqkwdeac0edp2ikk3hx9kzag</guid>
</item>

<item>
  <title>Elevated authentication errors on the API and SDK</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:48:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 15 Jun 2026 21:30:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmqfrexm90d5s2ik788efksz5</link>
  <guid>https://status.composio.dev/incident/cmqfrexm90d5s2ik788efksz5</guid>
</item>

<item>
  <title>MCP Servers endpoint returning errors</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 11 Jun 2026 11:00:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmq9nrvzw0171pdlz1fda2wh5</link>
  <guid>https://status.composio.dev/incident/cmq9nrvzw0171pdlz1fda2wh5</guid>
</item>

<item>
  <title>Degraded - Linear connection refresh </title>
  <description>
    Type: Incident
    Duration: 7 hours and 20 minutes

    Affected Components: Linear Auth
    Jun 10, 09:42:00 GMT+0 - Investigating - 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. 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.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:42:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:19:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 10 Jun 2026 09:42:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmq80nb7708nrqtwgv413wfk3</link>
  <guid>https://status.composio.dev/incident/cmq80nb7708nrqtwgv413wfk3</guid>
</item>

<item>
  <title>Certain customers are experiencing highly elevated API error rates</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:04:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Seeing highly elevated API rates for a small subset of accounts.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:32:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. The issue was caused due to a mistimed coordinated deployment. Approximately 2% of all incoming requests were impacted..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 9 Jun 2026 14:04:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmq6s399k00rwpkk4wz6f6uf1</link>
  <guid>https://status.composio.dev/incident/cmq6s399k00rwpkk4wz6f6uf1</guid>
</item>

<item>
  <title>Issues with Composio APIs</title>
  <description>
    Type: Incident
    

    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have identified the issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 May 2026 08:00:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpmd7t3z0amgnrlt5zyr50sa</link>
  <guid>https://status.composio.dev/incident/cmpmd7t3z0amgnrlt5zyr50sa</guid>
</item>

<item>
  <title>Valid Requests Being Blocked By Vercel Firewall</title>
  <description>
    Type: Incident
    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&#039;ve noticed Vercel&#039;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 &quot;cle:...&quot; or some other 3 letter region prefix please try again or reach out to us.  
This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;ve noticed Vercel&#039;s firewall has been blocking many tool execution requests and other requests to the backend..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:30:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 May 2026 01:00:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpmhcyqz0ps7p2mekehyk97a</link>
  <guid>https://status.composio.dev/incident/cmpmhcyqz0ps7p2mekehyk97a</guid>
</item>

<item>
  <title>Issues with Composio Platform</title>
  <description>
    Type: Incident
    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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 18 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:27:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:09:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Ability to create new connections was down.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 25 May 2026 23:09:22 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpltj6us0ivkp2n0taui7p14</link>
  <guid>https://status.composio.dev/incident/cmpltj6us0ivkp2n0taui7p14</guid>
</item>

<item>
  <title>Dashboard down</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:12:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:51:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 24 May 2026 18:30:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpkaxwcu007vpbmknq0c51dv</link>
  <guid>https://status.composio.dev/incident/cmpkaxwcu007vpbmknq0c51dv</guid>
</item>

<item>
  <title>Issues with Composio CLI</title>
  <description>
    Type: Incident
    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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 8 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  CLI auth was broken and all existing CLI auth was revoked hence functionally bricking CLI.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 24 May 2026 17:30:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpkax4n704thp2n0h1g58upe</link>
  <guid>https://status.composio.dev/incident/cmpkax4n704thp2n0h1g58upe</guid>
</item>

<item>
  <title>Issues with MCP connection creation</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 20 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 24 May 2026 02:30:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpkazjh604jjp2mem1swnpiq</link>
  <guid>https://status.composio.dev/incident/cmpkazjh604jjp2mem1swnpiq</guid>
</item>

<item>
  <title>Composio Outage</title>
  <description>
    Type: Incident
    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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 27 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:05:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:38:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Ability to create new connections was down.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 23 May 2026 09:38:27 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpi5one00755pbhlf1tfqmhr</link>
  <guid>https://status.composio.dev/incident/cmpi5one00755pbhlf1tfqmhr</guid>
</item>

<item>
  <title>All outgoing webhook &amp; trigger deliveries are facing an outage</title>
  <description>
    Type: Incident
    Duration: 5 hours and 43 minutes

    Affected Components: Triggers V2, Triggers V1
    May 22, 06:40:00 GMT+0 - Identified - 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. 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&#039;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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 43 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:08:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have implemented the configuration fix and monitoring.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:13:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. We&#039;re seeing full recovery on delivery volumes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 22 May 2026 01:30:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpgk6vx700grpcn90phoc7rm</link>
  <guid>https://status.composio.dev/incident/cmpgk6vx700grpcn90phoc7rm</guid>
</item>

<item>
  <title>Composio Security Incident</title>
  <description>
    Type: Incident
    Duration: 2 days and 34 minutes

    
    May 21, 18:59:26 GMT+0 - Identified - Learn more about here &lt;https://composio.dev/blog/composio-may-2026-security-incident&gt; May 25, 21:00:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 34 minutes</p>
    
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:59:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Learn more about here &lt;https://composio.dev/blog/composio-may-2026-security-incident&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 18:59:26 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpfuudag002cpbm2wv1qhjpf</link>
  <guid>https://status.composio.dev/incident/cmpfuudag002cpbm2wv1qhjpf</guid>
</item>

<item>
  <title>Degraded performance on Github connections</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:58:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:01:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:42:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 17:58:19 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpfsnsg90241niri0xup1jnu</link>
  <guid>https://status.composio.dev/incident/cmpfsnsg90241niri0xup1jnu</guid>
</item>

<item>
  <title>Degraded performance on connected account read and tool execution</title>
  <description>
    Type: Incident
    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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:19:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:33:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 12:19:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpfi4j12012vnr168a4omq9r</link>
  <guid>https://status.composio.dev/incident/cmpfi4j12012vnr168a4omq9r</guid>
</item>

<item>
  <title>Degraded performance for upload/download actions</title>
  <description>
    Type: Incident
    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&#039;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&#039;ll share updates soon. May 21, 13:19:48 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:35:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;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&#039;ll share updates soon..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:19:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 10:35:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpfelw8b008mpd7n2obsl59d</link>
  <guid>https://status.composio.dev/incident/cmpfelw8b008mpd7n2obsl59d</guid>
</item>

<item>
  <title>Tool executions failing</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:27:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:36:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 10:27:30 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpfck1e008wonrn68c7s6oel</link>
  <guid>https://status.composio.dev/incident/cmpfck1e008wonrn68c7s6oel</guid>
</item>

<item>
  <title>Degraded search latency using `sessions.search` or `COMPOSIO_SEARCH_TOOLS` on a subset of requests</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:53:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Investing an issue with search performance being intermittently degraded.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:18:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 18 May 2026 19:00:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmpc8wggh02l7qpqls8e04oto</link>
  <guid>https://status.composio.dev/incident/cmpc8wggh02l7qpqls8e04oto</guid>
</item>

<item>
  <title>Slack triggers are degraded</title>
  <description>
    Type: Incident
    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: &lt;https://slack-status.com/2026-05/fe557ca05fdb64fa&gt;. We are closely monitoring the situation and will update as things progress on slack&#039;s end. May 14, 15:06:00 GMT+0 - Monitoring - Slack&#039;s systems are still degraded (&lt;https://slack-status.com/2026-05/fe557ca05fdb64fa&gt;). But, we are seeing some early signs of recovery on slack&#039;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&#039;re now seeing near full recovery for slack triggers as slack systems come back online: &lt;https://slack-status.com/2026-05/fe557ca05fdb64fa&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 16 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:04:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident impacting slack triggers on the platform.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:54:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have confirmed that our systems are operational, but we are experiencing issues on slack events ingress due to an ongoing slack outage: &lt;https://slack-status.com/2026-05/fe557ca05fdb64fa&gt;. We are closely monitoring the situation and will update as things progress on slack&#039;s end..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:06:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Slack&#039;s systems are still degraded (&lt;https://slack-status.com/2026-05/fe557ca05fdb64fa&gt;). But, we are seeing some early signs of recovery on slack&#039;s end, the ingress volume is still unstable and fluctuating rapidly. Webhook deliveries may be delayed or missed. We are closely monitoring the situation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Slack triggers should now be back up again! We&#039;re now seeing near full recovery for slack triggers as slack systems come back online: &lt;https://slack-status.com/2026-05/fe557ca05fdb64fa&gt;.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 14 May 2026 14:04:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmp5ludlg0560npmzjcdeuo3z</link>
  <guid>https://status.composio.dev/incident/cmp5ludlg0560npmzjcdeuo3z</guid>
</item>

<item>
  <title>We have identified an issue in our Platform APIs</title>
  <description>
    Type: Incident
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:51:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:01:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:02:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 8 May 2026 10:51:00 +0000</pubDate>
  <link>https://status.composio.dev/incident/cmowswvac03fqco53srkzss4j</link>
  <guid>https://status.composio.dev/incident/cmowswvac03fqco53srkzss4j</guid>
</item>

  </channel>
  </rss>