Composio Outage History

13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Composio status99.82% uptime history

Every Recorded Composio Incident

Composio incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Elevated errors in Composio Sessions Search9 minResolved
Oct 26, 2026Elevated errors in Composio Platform7 minResolved
Oct 25, 2026Issues with Composio Platform34 minResolved
Oct 23, 2026Platform APIs returning errors13 minResolved
Oct 22, 2026Code Interpreter failures23h 50mResolved
Oct 22, 2026Trigger failures for Workday, Salesforce and Canvas18h 56mResolved
Oct 21, 2026Elevated Latency on Certain Endpoints1h 34mResolved
Oct 5, 2026Discord Bot toolkit is not available for tool executions54h 24mResolved
Oct 2, 2026Elevated errors in Instagram toolkit1h 36mResolved
Sep 18, 2026Authentication related issues on dashboard and for you (CLI and MCP)8 minResolved
Sep 17, 2026Elevated errors on platform APIs35 minResolved
Aug 24, 2026API Latencies are elevated1h 31mResolved
Aug 22, 2026Facing rate limits on Composio Managed Quickbooks App2h 57mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Composio incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Composio Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Composio acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Composio outage in this window ran 2d 6h, against a mean recovery of 8h 12m. If you depend on Composio in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.