Snapshot 310039
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
<?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>Wed, 18 Nov 2026 18:01:29 +0000</pubDate> <item> <title>Files capabilities in Sandboxes / Workbench are degraded</title> <description> Type: Incident Duration: 5 hours and 14 minutes Affected Components: Sandbox Nov 18, 20:21:00 GMT+0 - Resolved - Between approximately 17:20 and 18:20 UTC on 18 November, some Sandbox and Workbench sessions failed to start or could not access files. Service recovered at about 18:20 UTC and has been stable since. Nov 18, 18:01:29 GMT+0 - Investigating - We are currently investigating this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 5 hours and 14 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>20:21:00</var> GMT+0</small><br><strong>Resolved</strong> - Between approximately 17:20 and 18:20 UTC on 18 November, some Sandbox and Workbench sessions failed to start or could not access files. Service recovered at about 18:20 UTC and has been stable since..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>18:01:29</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> </content:encoded> <pubDate>Wed, 18 Nov 2026 18:01:29 +0000</pubDate> <link>https://status.composio.dev/incident/cmwmfh14k039g1nntly0pq1bi</link> <guid>https://status.composio.dev/incident/cmwmfh14k039g1nntly0pq1bi</guid> </item> <item> <title>Outlook toolkit degraded (upstream Microsoft outage)</title> <description> Type: Incident Duration: 1 day and 2 hours Affected Components: Outlook Nov 13, 21:00:00 GMT+0 - Resolved - Outlook triggers that were disabled during the Microsoft outage have been re-enabled. If a trigger is still off, reconnect your Outlook account and enable it again. Nov 13, 17:32:37 GMT+0 - Monitoring - Microsoft has largely recovered. We’re working on re-enabling affected triggers. In the meantime, you can re-enable a trigger from the dashboard or via the API. Events during the outage window may not have been delivered. Nov 12, 19:50:50 GMT+0 - Identified - Microsoft is tracking this on their side. Follow their updates at <https://status.cloud.microsoft> (Microsoft 365 service health). Outlook tool calls will recover once Microsoft resolves it; other toolkits are not affected. Nov 12, 19:00:00 GMT+0 - Identified - Outlook tool calls and triggers are failing or slow due to an ongoing Microsoft 365 / Exchange Online outage. Other toolkits are not affected. We’re monitoring and will update once Microsoft recovers. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 day and 2 hours</p> <p><strong>Affected Components:</strong> </p> <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Resolved</strong> - Outlook triggers that were disabled during the Microsoft outage have been re-enabled. If a trigger is still off, reconnect your Outlook account and enable it again..</p> <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>17:32:37</var> GMT+0</small><br><strong>Monitoring</strong> - Microsoft has largely recovered. We’re working on re-enabling affected triggers. In the meantime, you can re-enable a trigger from the dashboard or via the API. Events during the outage window may not have been delivered..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>19:50:50</var> GMT+0</small><br><strong>Identified</strong> - Microsoft is tracking this on their side. Follow their updates at <https://status.cloud.microsoft> (Microsoft 365 service health). Outlook tool calls will recover once Microsoft resolves it; other toolkits are not affected..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - Outlook tool calls and triggers are failing or slow due to an ongoing Microsoft 365 / Exchange Online outage. Other toolkits are not affected. We’re monitoring and will update once Microsoft recovers..</p> ]]> </content:encoded> <pubDate>Thu, 12 Nov 2026 19:00:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmwdylbqx022h1mp9txc8dzqm</link> <guid>https://status.composio.dev/incident/cmwdylbqx022h1mp9txc8dzqm</guid> </item> <item> <title>Elevated errors on Composio Connect MCP</title> <description> Type: Incident Duration: 7 hours Affected Components: Composio Connect MCP Oct 30, 05:27:00 GMT+0 - Resolved - Between 05:20 and 05:27 UTC on 30 October, requests to Composio Connect MCP returned errors, and users could not start or use MCP sessions. The cause was a faulty deployment, which we rolled back at 05:27 UTC. A permanent fix has been deployed since. Oct 30, 05:20:00 GMT+0 - Identified - </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 7 hours</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>05:27:00</var> GMT+0</small><br><strong>Resolved</strong> - Between 05:20 and 05:27 UTC on 30 October, requests to Composio Connect MCP returned errors, and users could not start or use MCP sessions. The cause was a faulty deployment, which we rolled back at 05:27 UTC. A permanent fix has been deployed since..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>05:20:00</var> GMT+0</small><br><strong>Identified</strong> - .</p> ]]> </content:encoded> <pubDate>Fri, 30 Oct 2026 05:20:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmvvd5gzl0gyp13li5957r8oi</link> <guid>https://status.composio.dev/incident/cmvvd5gzl0gyp13li5957r8oi</guid> </item> <item> <title>Elevated errors in Composio Sessions Search</title> <description> Type: Incident Duration: 8 minutes Affected Components: Tool Search Oct 26, 08:25:00 GMT+0 - Resolved - This incident has been resolved. Oct 26, 08:05:00 GMT+0 - Identified - We have identified the issue and fix is in progress </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 8 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>08:25:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>08:05:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and fix is in progress.</p> ]]> </content:encoded> <pubDate>Mon, 26 Oct 2026 08:05:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmvozm3b10asx13peeru3uc6k</link> <guid>https://status.composio.dev/incident/cmvozm3b10asx13peeru3uc6k</guid> </item> <item> <title>Elevated errors in Composio Platform</title> <description> Type: Incident Duration: 6 minutes Affected Components: MCP Servers, Sandbox, Triggers V2, Composio Connect MCP, Composio CLI, Triggers V1, Dashboard, Tool Execution, Proxy, Tool Search, Connections, v3 API Oct 26, 00:35:00 GMT+0 - Resolved - This incident has been resolved. Oct 26, 00:30:00 GMT+0 - Investigating - We are having a partial outage with some API requests returning 500\. We're working with our infrastructure provider to find the root cause of the disruptions. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 6 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>00:35:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are having a partial outage with some API requests returning 500\. We're working with our infrastructure provider to find the root cause of the disruptions..</p> ]]> </content:encoded> <pubDate>Mon, 26 Oct 2026 00:30:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmvoj5k7400kh1fpeiryjjrgn</link> <guid>https://status.composio.dev/incident/cmvoj5k7400kh1fpeiryjjrgn</guid> </item> <item> <title>Elevated errors with Composio Platform</title> <description> Type: Incident Duration: 11 hours and 37 minutes Affected Components: MCP Servers, Sandbox, Triggers V2, Composio Connect MCP, Composio CLI, Triggers V1, Dashboard, Tool Execution, Proxy, Tool Search, Connections, v3 API Oct 25, 06:05:00 GMT+0 - Resolved - The 500s have resolved. Oct 25, 05:55:00 GMT+0 - Investigating - The Composio Platform is experiencing a partial outage with some API requests returning 500. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 11 hours and 37 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>06:05:00</var> GMT+0</small><br><strong>Resolved</strong> - The 500s have resolved..</p> <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>05:55:00</var> GMT+0</small><br><strong>Investigating</strong> - The Composio Platform is experiencing a partial outage with some API requests returning 500..</p> ]]> </content:encoded> <pubDate>Sun, 25 Oct 2026 05:55:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmvnfa47107lg1bnbmypd29p9</link> <guid>https://status.composio.dev/incident/cmvnfa47107lg1bnbmypd29p9</guid> </item> <item> <title>Elevated errors on Composio platform</title> <description> Type: Incident Duration: 10 minutes Affected Components: MCP Servers, Sandbox, Triggers V2, Composio Connect MCP, Composio CLI, Triggers V1, Dashboard, Tool Execution, Proxy, Tool Search, Connections, v3 API Oct 23, 10:49:52 GMT+0 - Resolved - This incident has been resolved. Oct 23, 10:39:45 GMT+0 - Investigating - We are currently investigating this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 10 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>10:49:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>10:39:45</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> </content:encoded> <pubDate>Fri, 23 Oct 2026 10:39:45 +0000</pubDate> <link>https://status.composio.dev/incident/cmvku8u66073j0wph82m468ou</link> <guid>https://status.composio.dev/incident/cmvku8u66073j0wph82m468ou</guid> </item> <item> <title>Code Interpreter failures</title> <description> Type: Incident Duration: 23 hours and 47 minutes Affected Components: Code Interpreter Oct 23, 17:47:14 GMT+0 - Resolved - The code interpreter toolkit has been disabled as part of security hardening measures. As we work on redesigning it we suggest using Remote Sandbox ([https://docs.composio.dev/docs/sandbox/remote)](https://docs.composio.dev/docs/sandbox/remote) for code executions. Oct 22, 18:00:00 GMT+0 - Investigating - We're investigating failures with Code Interpreter as a tool execution giving false retirement notices. This incident doesn't impact any other toolkits at the moment. </description> <content:encoded> < for code executions. .</p> <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We're investigating failures with Code Interpreter as a tool execution giving false retirement notices. This incident doesn't impact any other toolkits at the moment..</p> ]]> </content:encoded> <pubDate>Thu, 22 Oct 2026 18:00:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmvjv3tu100zr1as0s0bau0vc</link> <guid>https://status.composio.dev/incident/cmvjv3tu100zr1as0s0bau0vc</guid> </item> <item> <title>Trigger failures for Workday, Salesforce and Canvas</title> <description> Type: Incident Duration: 18 hours and 55 minutes Affected Components: Workday, Salesforce, Canvas Oct 23, 12:22:00 GMT+0 - Resolved - This incident has been resolved. Oct 22, 17:26:34 GMT+0 - Investigating - We are currently investigating this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 18 hours and 55 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>12:22:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>17:26:34</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> </content:encoded> <pubDate>Thu, 22 Oct 2026 17:26:34 +0000</pubDate> <link>https://status.composio.dev/incident/cmvjtc53l00hf0ws0z2h2rexe</link> <guid>https://status.composio.dev/incident/cmvjtc53l00hf0ws0z2h2rexe</guid> </item> <item> <title>Elevated Latency on Certain Endpoints</title> <description> Type: Incident Duration: 1 hour and 33 minutes Affected Components: MCP Servers, Sandbox, Triggers V2, Triggers V1, Tool Execution, Proxy, Tool Search, Connections, v3 API Oct 21, 21:07:49 GMT+0 - Resolved - This incident has been resolved. Oct 21, 20:34:11 GMT+0 - Monitoring - We are seeing latency recover. Oct 21, 19:34:49 GMT+0 - Investigating - We are investigating an increased latency on certain API endpoints. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 33 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>21:07:49</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>20:34:11</var> GMT+0</small><br><strong>Monitoring</strong> - We are seeing latency recover..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>19:34:49</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating an increased latency on certain API endpoints..</p> ]]> </content:encoded> <pubDate>Wed, 21 Oct 2026 19:34:49 +0000</pubDate> <link>https://status.composio.dev/incident/cmviih7wz04zg0wmke8tdyn32</link> <guid>https://status.composio.dev/incident/cmviih7wz04zg0wmke8tdyn32</guid> </item> <item> <title> Connect links showing "Invalid or expired link"</title> <description> Type: Incident Duration: 13 hours and 20 minutes Affected Components: Dashboard, Connections Oct 20, 18:50:00 GMT+0 - Resolved - This incident is resolved. Between 05:30 and 18:05 UTC on October 20, some end users who opened a Connect link saw an "Invalid or expired link" error and couldn't connect their accounts. The cause was a new rate limit that was applied too strictly to Connect link lookups. We've fixed it and are reviewing how we roll out rate-limit changes so this doesn't happen again. No other APIs or features were affected, and no data was lost or exposed. We're sorry for the disruption. Oct 20, 18:05:00 GMT+0 - Monitoring - A fix has been deployed, and Connect links are loading normally again. We're watching closely to make sure the issue is fully resolved. If your users couldn't connect an account earlier, they can open the same Connect link again or you can generate a new one. Oct 20, 17:00:00 GMT+0 - Identified - We've found the cause. A recent change that limits how often Connect links can be looked up is rejecting valid links when traffic is high. We're preparing a fix. Retrying the link after a few minutes may still work in the meantime. We've also noticed the error rates are elevated to about 20%. Oct 20, 05:30:00 GMT+0 - Investigating - We're investigating reports that some end users see an "Invalid or expired link" error when they open a Connect link, which stops them from connecting their accounts. Other APIs and features are working normally. We'll post another update as soon as we know more. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 13 hours and 20 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Between 05:30 and 18:05 UTC on October 20, some end users who opened a Connect link saw an "Invalid or expired link" error and couldn't connect their accounts. The cause was a new rate limit that was applied too strictly to Connect link lookups. We've fixed it and are reviewing how we roll out rate-limit changes so this doesn't happen again. No other APIs or features were affected, and no data was lost or exposed. We're sorry for the disruption..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:05:00</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been deployed, and Connect links are loading normally again. We're watching closely to make sure the issue is fully resolved. If your users couldn't connect an account earlier, they can open the same Connect link again or you can generate a new one..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We've found the cause. A recent change that limits how often Connect links can be looked up is rejecting valid links when traffic is high. We're preparing a fix. Retrying the link after a few minutes may still work in the meantime. We've also noticed the error rates are elevated to about 20%..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>05:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We're investigating reports that some end users see an "Invalid or expired link" error when they open a Connect link, which stops them from connecting their accounts. Other APIs and features are working normally. We'll post another update as soon as we know more..</p> ]]> </content:encoded> <pubDate>Tue, 20 Oct 2026 05:30:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmvh1hz8200oo1nqo3tht5xkp</link> <guid>https://status.composio.dev/incident/cmvh1hz8200oo1nqo3tht5xkp</guid> </item> <item> <title>Elevated errors on Composio Platform</title> <description> Type: Incident Duration: 5 minutes Affected Components: MCP Servers, Linear Auth, Quickbooks, Sandbox, Triggers V2, Github Auth, Google Auth, Twitter Auth, Dashboard, Composio Connect MCP, Composio CLI, Triggers V1, Tool Execution, Proxy, Tool Search, Connections, v3 API Oct 15, 11:10:00 GMT+0 - Resolved - This incident has been resolved. Oct 15, 11:05:00 GMT+0 - Identified - </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 5 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>11:10:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>11:05:00</var> GMT+0</small><br><strong>Identified</strong> - .</p> ]]> </content:encoded> <pubDate>Thu, 15 Oct 2026 11:05:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmv9gfh5n00v41noy6r7kb73q</link> <guid>https://status.composio.dev/incident/cmv9gfh5n00v41noy6r7kb73q</guid> </item> <item> <title>Elevated errors on Composio Connect MCP</title> <description> Type: Incident Duration: 7 hours and 58 minutes Affected Components: Composio Connect MCP Oct 7, 03:40:00 GMT+0 - Resolved - 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. Oct 6, 19:42:00 GMT+0 - Investigating - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 7 hours and 58 minutes</p> <p><strong>Affected Components:</strong> </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> <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> ]]> </content:encoded> <pubDate>Tue, 6 Oct 2026 19:42:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmuxlzwoi00a81mry5wov5ly3</link> <guid>https://status.composio.dev/incident/cmuxlzwoi00a81mry5wov5ly3</guid> </item> <item> <title>Discord Bot toolkit is not available for tool executions</title> <description> Type: Incident Duration: 2 days and 6 hours Affected Components: Discord Bot Oct 7, 17:29:55 GMT+0 - Resolved - 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. Oct 5, 11:30:00 GMT+0 - Investigating - The Discord Bot toolkit is temporarily unavailable while we make important design improvements. We're also evaluating whether we'll continue to support Composio-managed Discord bot connections. Discord Bot tool calls will return an error until the toolkit is back. We'll share an update soon. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 2 days and 6 hours</p> <p><strong>Affected Components:</strong> </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> <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're also evaluating whether we'll continue to support Composio-managed Discord bot connections. Discord Bot tool calls will return an error until the toolkit is back. We'll share an update soon..</p> ]]> </content:encoded> <pubDate>Mon, 5 Oct 2026 11:30:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmuvm6vt606l21mjwr2aokusg</link> <guid>https://status.composio.dev/incident/cmuvm6vt606l21mjwr2aokusg</guid> </item> <item> <title>Elevated errors in Instagram toolkit</title> <description> Type: Incident Duration: 1 hour and 34 minutes Affected Components: INSTAGRAM Oct 2, 21:40:32 GMT+0 - Resolved - 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. Oct 2, 20:40:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 2, 20:07:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 34 minutes</p> <p><strong>Affected Components:</strong> </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> <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'>20:07:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> </content:encoded> <pubDate>Fri, 2 Oct 2026 20:07:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmurgng9a011014l6pv0qtrhv</link> <guid>https://status.composio.dev/incident/cmurgng9a011014l6pv0qtrhv</guid> </item> <item> <title>Authentication related issues on dashboard and for you (CLI and MCP)</title> <description> Type: Incident Duration: 8 minutes Affected Components: Dashboard, Composio Connect MCP, Composio CLI Sep 18, 23:06:11 GMT+0 - Resolved - This incident has been resolved. Sep 18, 23:00:06 GMT+0 - Identified - One of our vendors, workos is facing elevated API failures <https://status.workos.com/> Sep 18, 22:58:24 GMT+0 - Investigating - We are currently investigating this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 8 minutes</p> <p><strong>Affected Components:</strong> </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'>23:00:06</var> GMT+0</small><br><strong>Identified</strong> - One of our vendors, workos is facing elevated API failures <https://status.workos.com/>.</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:encoded> <pubDate>Fri, 18 Sep 2026 22:58:24 +0000</pubDate> <link>https://status.composio.dev/incident/cmu7k7wtk06lw0wrudzkbk8e3</link> <guid>https://status.composio.dev/incident/cmu7k7wtk06lw0wrudzkbk8e3</guid> </item> <item> <title>Elevated errors on platform APIs</title> <description> Type: Incident Duration: 21 minutes Affected Components: MCP Servers, Sandbox, Triggers V2, v3 API, Dashboard, Composio Connect MCP, Composio CLI, Triggers V1, Tool Execution, Proxy, Tool Search, Connections Sep 17, 06:56:00 GMT+0 - Resolved - The incident has been resolved. Sep 17, 06:40:00 GMT+0 - Investigating - We are currently investigating this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 21 minutes</p> <p><strong>Affected Components:</strong> </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> <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> ]]> </content:encoded> <pubDate>Thu, 17 Sep 2026 06:40:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmu56ait702uc13uikzdajbmu</link> <guid>https://status.composio.dev/incident/cmu56ait702uc13uikzdajbmu</guid> </item> <item> <title>Webhook Triggers Degraded</title> <description> Type: Incident Duration: 1 hour and 10 minutes Affected Components: Triggers V2, Triggers V1 Sep 2, 20:30:00 GMT+0 - Resolved - This incident has been resolved. Backlog of webhook payloads is cleared now. Sep 2, 19:50:00 GMT+0 - Monitoring - 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. Sep 2, 19:20:00 GMT+0 - Identified - Webhook based triggers processing is degraded. Polling based triggers continue to function as expected. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 10 minutes</p> <p><strong>Affected Components:</strong> </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> <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> ]]> </content:encoded> <pubDate>Wed, 2 Sep 2026 19:20:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmtmmzhpd09021aqq06819cru</link> <guid>https://status.composio.dev/incident/cmtmmzhpd09021aqq06819cru</guid> </item> <item> <title>API Latencies are elevated</title> <description> Type: Incident Duration: 1 hour and 29 minutes Affected Components: Triggers V2, v3 API, Triggers V1 Aug 24, 11:29:15 GMT+0 - Resolved - This incident has been resolved. Our latency numbers are looking good and slack triggers continue to work now. Aug 24, 11:00:44 GMT+0 - Monitoring - Slack triggers are turned off as part of remediation of platform latencies. Aug 24, 10:16:53 GMT+0 - Investigating - We are currently investigating this incident. Aug 24, 10:00:00 GMT+0 - Investigating - We are currently investigating this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 29 minutes</p> <p><strong>Affected Components:</strong> </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> <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'>10:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> </content:encoded> <pubDate>Mon, 24 Aug 2026 10:00:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmt744lhn1rzq0zmedz4bgfw3</link> <guid>https://status.composio.dev/incident/cmt744lhn1rzq0zmedz4bgfw3</guid> </item> <item> <title>Facing rate limits on Composio Managed Quickbooks App</title> <description> Type: Incident Duration: 2 hours and 55 minutes Affected Components: Quickbooks Aug 23, 02:41:41 GMT+0 - Resolved - This incident has been resolved. Rate limits have been upgraded. Aug 23, 02:41:03 GMT+0 - Identified - We are continuing to work on a fix for this incident. Aug 22, 23:47:00 GMT+0 - Investigating - We are currently investigating this incident. But, we recommend you moving your production workflows to your own OAuth apps. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 2 hours and 55 minutes</p> <p><strong>Affected Components:</strong> </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> <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'> 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> ]]> </content:encoded> <pubDate>Sat, 22 Aug 2026 23:47:00 +0000</pubDate> <link>https://status.composio.dev/incident/cmt540sm319yu0kpbh0n74x9i</link> <guid>https://status.composio.dev/incident/cmt540sm319yu0kpbh0n74x9i</guid> </item> <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're monitoring the third party (WorkOs) status for any new updates here: <https://status.workos.com> 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, 08:08:00 GMT+0 - Investigating - We are currently investigating this incident. </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> <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're monitoring the third party (WorkOs) status for any new updates here: <https://status.workos.com>.</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> <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> ]]> </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, 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. 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: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, 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. </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> <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's regression in the new-email polling logic. We're adding checks to prevent recurrence, and we're sorry for the disruption..</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've reverted the change and webhook delivery has resumed. We're actively monitoring to confirm full recovery..</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'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'>04:48:00</var> GMT+0</small><br><strong>Investigating</strong> - We're investigating reports that the GMAIL\_NEW\_GMAIL\_MESSAGE trigger has stopped delivering webhooks for a subset of accounts..</p> ]]> </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:29:58 GMT+0 - Resolved - This incident has been resolved. 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: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. </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> <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> <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: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> ]]> </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 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. Jun 27, 10:40:00 GMT+0 - Investigating - We are currently investigating this incident. </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> <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> <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> ]]> </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:45:00 GMT+0 - Resolved - This incident has been resolved. Tool executions across the impacted toolkits across all versions are now working normally. 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: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 </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 41 minutes</p> <p><strong>Affected Components:</strong> </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> <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'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: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> ]]> </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> </channel> </rss>