Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Support

System status

Real-time uptime + incident history for every Dock surface lives at status.trydock.ai. Check it before filing a "Dock is broken" ticket.

What we monitor

  • Web, trydock.ai, dashboard, login flow, sign-up gate
  • REST API, every /api/* endpoint, p50 + p99 latency per endpoint
  • MCP server, /api/mcp endpoint, OAuth flow, tool execution latency
  • Webhooks, delivery success rate, queue depth, retry rate
  • Real-time stream, SSE event delivery, poll-fallback latency
  • Database, Neon Postgres connection pool, read + write latency

Subscribe to incidents

Get pinged on incidents and post-mortems via:

Active incident

If a service is down right now, the status page banner is the canonical source. Don't take our word for it from anywhere else; the page updates within 60 seconds of detection.

Historical uptime

90-day uptime history is published per service. Long-window (year+) trends summarize at the bottom of the status page.

Frequently asked questions

Where is Dock's status page?
`status.trydock.ai`. Real-time uptime + active incidents + 90-day history per service (web app, API, MCP server, webhooks, email delivery). Also linked from the dashboard footer + every error page.
Is Dock down right now?
Check `status.trydock.ai` for the live uptime. If everything's green there but you're seeing errors, it might be a regional or per-account issue; file a support ticket with the `x-request-id` from the failing request.
How do I subscribe to Dock incident updates?
RSS feed at `status.trydock.ai/feed`. Or email subscription via the status page (Subscribe button). Webhook subscriptions for posting to your team's Slack on the roadmap.
What's Dock's uptime SLA?
99.9% on Pro tier, 99.95% on Scale, best-effort on Free. Service credits per the SLA terms if we miss it. Historical uptime is consistently above SLA; check status.trydock.ai for the trailing-90d numbers.
How does Dock notify me about incidents?
Status page updates in real time. Subscribers get email + RSS within minutes of an incident being declared. Critical incidents (data loss, auth broken, security): email to org owners directly within 1 hour.
How long does Dock take to resolve incidents?
Median time-to-resolve: 15 minutes for routine issues, 1-2 hours for complex outages. Severity 1 (full outage): on-call paged immediately, mitigation usually within 15 minutes; full root-cause within 24h.
Does Dock publish post-mortems?
Yes for any user-affecting incident over 15 minutes. Posted to status.trydock.ai/incidents within 5 business days. Includes timeline, root cause, customer impact, follow-up actions.
What was Dock's last major outage?
Check status.trydock.ai/incidents for the full list; we mark severity per incident. Most outages are <30 min; the worst tend to be Postgres-related (and trigger our pager + the same-day post-mortem).
Does Dock have scheduled maintenance windows?
Rarely. Most deploys are zero-downtime (blue-green via Vercel). Migrations that require brief unavailability are scheduled off-hours (Saturday early morning UTC) and announced 48h in advance via the status page.
Can my AI agent check Dock's status programmatically?
Yes. `GET https://status.trydock.ai/api/v1/components` returns the current operational status of every Dock service in JSON. Useful for agents that should pause writes during a known incident; webhook subscription for status changes is on the roadmap.
Updated