Vendor record
Convex
Checked
Front door check counts and Convex’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Convex endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,878 of 2,878 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.convex.dev
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Convex product, region or your app worked.
How we count front door checksConvex says
Incident posts from Convex’s status page, with its titles, impact levels and times. They say what Convex chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
19
incidents Convex posted, last 1 year
Median recorded duration: 1h 5m. From 19 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Failing function calls
MajorConvex’s postStarted, per Convex
Closed in our record(36m)
AI gateway unavailable
CriticalConvex’s postStarted, per Convex
Closed in our record(1h 5m)
Dashboard logins degraded
Not specifiedConvex’s postStarted, per Convex
Closed in our record(1h 9m)
Account verification/team invite emails not working
MajorConvex’s postStarted, per Convex
Closed in our record(1h 56m)
Some HTTP Actions returning 404
MinorConvex’s postStarted, per Convex
Closed in our record(28m)
14 older records
New deployments unable to push functions to Convex
MinorConvex’s postStarted, per Convex
Closed in our record(1h 4m)
Automatic backups are not running
MinorConvex’s postStarted, per Convex
Closed in our record(1h 25m)
High error rates across all deployments, except some D1024s
MajorConvex’s postStarted, per Convex
Closed in our record(17m)
Spike in error rates for Convex Free and Starter deployments
MinorConvex’s postStarted, per Convex
Closed in our record(10m)
Elevated error rate on some Pro deployments
MinorConvex’s postStarted, per Convex
Closed in our record(2h 57m)
Subset of EU deployments seeing elevated errors
MinorConvex’s postStarted, per Convex
Closed in our record(1h 47m)
Custom domain creation encountering errors
MinorConvex’s postStarted, per Convex
Closed in our record(1h 12m)
Incident Affecting Some Deployments
MajorConvex’s postStarted, per Convex
Closed in our record(3h 58m)
Intermittent Impact from Upstream Infrastructure Outage
MajorConvex’s postStarted, per Convex
Closed in our record(1h 53m)
Elevated latency for function calls for some deployments
MinorConvex’s postStarted, per Convex
Closed in our record(46m)
Login/Deployment/Dashboard services impacted
CriticalConvex’s postStarted, per Convex
Closed in our record(37m)
Small percentage of deployments experiencing outage
MajorConvex’s postStarted, per Convex
Closed in our record(31m)
Some deployments are unavailable
MinorConvex’s postStarted, per Convex
Closed in our record(34m)
elevated latency for a small subset of convex deployments
MinorConvex’s postStarted, per Convex
Closed in our record(3h 23m)
Your code, your dependencies
See which of your code paths call Convex
Connect GitHub or GitLab to find where your public or private repository uses Convex. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Convex status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Convex currently down?
Convex's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Convex last have an outage?
The most recent closed incident record began 6 days ago and spans 36 minutes. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Convex?
No. CheckUpstream checks Convex’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Convex in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Convex?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.