System status
Operational

All systems operational

Last updated ·Refresh 30s·Components 9·90d uptime 99.97%
/ Components

Each surface, all the way down

90-day uptime per surface. Each square is one day — green is healthy, amber is a degraded window, red is an outage.

ok warn fail
  • Web app

    dispatch.app · Dashboard, builder, and marketing surfaces

    90 days agotoday
    Operational
    99.99%
    0 incidents · 30d
  • API · Parse + Execute

    Plain-English parser and run executor

    90 days agotoday
    Operational
    99.98%
    0 incidents · 30d
  • Workflow runner

    Phase planner, retries, and live phase events

    90 days agotoday
    Operational
    99.97%
    1 incident · 30d
  • Cron scheduler

    Time-based triggers · UTC clock + per-flow timezones

    90 days agotoday
    Operational
    99.95%
    1 incident · 30d
  • Webhook triggers

    Inbound HTTPS triggers, signing, and replay protection

    90 days agotoday
    Operational
    99.99%
    0 incidents · 30d
  • Integration · AI providers

    OpenAI, Anthropic, Google · upstream availability

    90 days agotoday
    Operational
    99.92%
    1 incident · 30d
  • Integration · Google services

    Gmail, Drive, Calendar · OAuth + API surfaces

    90 days agotoday
    Operational
    99.96%
    0 incidents · 30d
  • Integration · Apps

    Slack, Discord, GitHub, Linear, Stripe, Notion

    90 days agotoday
    Operational
    99.98%
    0 incidents · 30d
  • Database · Upstash Redis / Vercel KV

    State store, run history, and audit log

    90 days agotoday
    Operational
    100.00%
    0 incidents · 30d
/ Live ping

Measured from your browser, right now

Every fifteen seconds your browser pings the Dispatch edge. The number on the right is your real round-trip — not a marketing average.

Edge round-trip
n/ams

Couldn't reach the edge from this browser. Check your connection.

P50
38 ms
P95
142 ms
P99
284 ms
/ Incidents

Past 90 days · incidents

Every incident, post-mortem-grade. We file these from the audit log — not after the fact.

No active incidents
  1. 2026-04-15 · 14:22 UTCMinor 4m resolved

    Cron scheduler delay

    Scheduled runs queued behind a deploy rolling forward across regions. Runs were dispatched within 4 minutes of their cron time. No data loss.

  2. 2026-03-28 · 09:15 UTCMajor 12m resolved by failover

    Anthropic API upstream issue

    Anthropic returned elevated 5xx for ~12 minutes. Dispatch automatically failed AI-Prompt nodes over to OpenAI for affected workflows that opted into multi-provider routing.

Notifications

Get notified about incidents

One email when something breaks. One email when it's back. Nothing in between.

RSS · /status.rss·Slack webhook · paid plans·SMS · enterprise