CheckUpstream measured Convex at 100.000% availability across 2827 independent checks (global · api). 17 incidents were recorded in the past 12 months; the most recent resolved 15 days ago after 2 hours. Status signals are polled from Convex's official Atlassian Statuspage status page, alongside independent probes and community reports.
180 days measured availability how this is computed
100.000%
global · api · n=2827 · p95 584ms (30d)
Share of our own checks against Convex endpoints that returned Convex's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 17 incidents · 174 of 180 days with none posted · 5h 6m of declared impact
Fewer incidents in the last 30 days than 25% of 232 tracked services.
Share of each window with no impact declared by Convex
7d
100.000%
30d
99.776%
90d
99.925%
180d
99.882%
1y
99.942%
Downtime like this can be refundable
If you're a paying Convex customer, outages in these windows may count against Convex's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Convex entitlement →Does Convex actually matter to you?
A Convex outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 17 incidents Convex published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Convex takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 16, 23:33 UTC · resolved in 1h 56m · Resolved
Aug 12, 03:41 UTC · resolved in 8m · Resolved
Aug 12, 03:41 UTC · resolved in 28m · Resolved
Live Convex status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/convex)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Convex is currently Operational. CheckUpstream tracks Convex in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Convex's last resolved incident started 15 days ago and lasted 1h 56m (a partial outage).
Looking for the live "is Convex down" view? See the Convex Live status page.
Jul 15, 05:35 UTC · resolved in 1h 4m · Resolved
May 22, 06:11 UTC · resolved in 3h 58m · Resolved
May 8, 00:16 UTC · resolved in 1h 53m · Resolved
May 6, 17:43 UTC · resolved in 46m · Resolved
Apr 21, 16:23 UTC · resolved in 37m · Resolved
Apr 9, 05:59 UTC · resolved in 31m · Resolved
Mar 25, 21:50 UTC · resolved in 34m · Resolved
Mar 25, 16:27 UTC · resolved in 3h 23m · Resolved
Convex's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Convex endpoints. It is the share of checks that returned the expected response, not a figure taken from Convex's status page.
Sign up to CheckUpstream and add Convex to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Convex's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.