Skip to content
New: Replays now compare against the last 90 days. Read the changelog

Status

Capstan status

All systems normal

Every component is working in the US and EU regions. Checked .

Planned: Database upgrade in the EU region

to · EU (Frankfurt)

We're upgrading the EU database. Runs keep going; the app may be slow to load for up to a minute.

Components

Region

Uptime over the last 90 days

Product

  • App

    Workspace, agent builder and run traces

    Operational

    100.00% uptime in the last 90 days, no incidents
  • API and SDKs

    REST API, TypeScript and Python SDKs, CLI

    Operational

    100.00% uptime in the last 90 days, no incidents
  • MCP server

    Capstan tools in Claude, Cursor and other clients

    Operational

    100.00% uptime in the last 90 days, no incidents

Agents

  • Agent runs

    Scheduling and running every step

    Operational

    99.98% uptime in the last 90 days, 1 day with an incident
  • Approvals

    Slack, Microsoft Teams and email

    Operational

    99.99% uptime in the last 90 days, 1 day with an incident
  • Replays

    Testing agents on past cases

    Operational

    99.97% uptime in the last 90 days, 1 day with an incident
  • Tool connections

    Stripe, Zendesk, HubSpot and 120 more

    Operational

    100.00% uptime in the last 90 days, no incidents
  • Webhooks

    Run and approval events to your endpoints

    Operational

    99.99% uptime in the last 90 days, 1 day with an incident

Third parties

  • AI model providers

    The models agent steps call

    Operational

    99.98% uptime in the last 90 days, 1 day with an incident
  • Email delivery

    Sign-in, approval and report emails

    Operational

    100.00% uptime in the last 90 days, no incidents

No incidentsDegraded performanceOutage

Past incidents

October 2026

Slow approvals in Microsoft Teams

Degraded performance · 47 min

Approvals · All regions

  1. Resolved ·

    Approval messages in Teams are arriving within seconds again. 212 approvals were delayed by up to 9 minutes; none were lost.

  2. Identified ·

    Microsoft's Bot Framework is rate-limiting our requests after a change on their side. We've slowed our retries and are working with Microsoft.

  3. Investigating ·

    Some approval requests in Microsoft Teams are arriving late. Slack and email approvals are not affected.

Replays waiting longer than usual to start

Degraded performance · 2 h 10 min

Replays · US (Virginia)

  1. Resolved ·

    The replay queue is back to normal. Every queued replay ran; none were dropped.

  2. Monitoring ·

    We've added capacity for replays and the queue is shrinking. Live agent runs were never affected.

  3. Investigating ·

    Replays in the US region are waiting up to 40 minutes to start, after a spike in 90-day replays.

September 2026

Agent runs failing in the EU region

Outage · 22 min

Agent runs, Replays · EU (Frankfurt)

  1. Resolved ·

    Runs are succeeding again. Runs that failed between 07:48 and 08:06 UTC were retried automatically from their last finished step; no step ran twice.

  2. Identified ·

    A database failover in Frankfurt left run workers pointing at the old primary. We're moving them to the new one.

  3. Investigating ·

    New agent runs in the EU region are failing to start. The US region is not affected.

August 2026

Delayed webhook deliveries

Degraded performance · 35 min

Webhooks · All regions

  1. Resolved ·

    Webhook deliveries are back to normal, and every delayed event has been delivered in order.

  2. Investigating ·

    Webhook events are being delivered up to 12 minutes late. Runs and approvals themselves are working.

Errors from one AI model provider

Degraded performance · 1 h 5 min

AI model providers, Agent runs · All regions

  1. Resolved ·

    The provider has fixed the issue. Steps that failed were retried automatically, and agents with a fallback model never stopped.

  2. Identified ·

    One model provider is returning errors for about 20% of requests. Agents with a fallback model are switching to it; others retry with backoff.

  3. Investigating ·

    Some agent steps are failing with model errors.

Get updates

An email when an incident starts, changes or ends, and before planned maintenance. Nothing else. Or follow the RSS feed.

Sample status data. Replace data/status.ts, or point the footer's status link at your hosted status page.