uptime
Status, with receipts.
Live status mirrors what you'd see at the public status page. Below: a 90-day historical strip per component, plus our SLA commitments. Pre-launch — these are commitments, not historical claims.
Per-component status
Per-component status
Each strip below is 90 daily cells. Green means no incidents observed; amber means a partial incident logged; red means a full outage logged. Empty cells mean we hadn't started measuring yet.
Pre-launch — the strip below is a placeholder shape until the synthetic monitor has 90 days of data. We started collecting on 2026-05-01.
orchestrator API
api.meetbot.dev — bot dispatch + status endpoints
last 90 days
bot fleet
fleet of meet/teams/zoom containers on Hetzner
last 90 days
S3 storage delivery
S3 multipart uploads to your bucket
last 90 days
webhook delivery
outbound webhook delivery + retries
last 90 days
dashboard (web)
meetbot.dev — marketing + admin + account
last 90 days
SLA commitments
SLA commitments
We publish targets, not aspirational copy. When we miss a target we write a public retrospective.
99.5% target on the orchestrator API
Measured: HTTP 5xx + 408 over total requests, excluding planned maintenance windows announced at least 72h ahead.
99.9% target on the dashboard + marketing site
Measured by external probes hitting / and /pricing every 60s.
99% target on first-attempt webhook delivery within 30s of meeting-end
Retries continue per the webhook spec; this metric is first-attempt only because that's the one customers feel.
Recent incidents
Recent incidents
No incidents logged yet. As we ship public infrastructure, post-mortems land here and at /blog?tag=incident.
Tracking since 2026-05-01. We publish raw incident retrospectives at /blog?tag=incident — don't trust the SLA claim, read the post-mortems.