Is Convex down?
For agents
proceed
Proceed.
GET upbutler.com/status/convex/status.agent.json
MCP: upstream_status {"service":"convex"}
Reactive backend: database, functions and scheduling.
What Convex reports
Operational
Taken as is from Convex's own status page API. Incident titles and component names below are theirs.
Open status.convex.devUpButler's independent probe
There is no keyless endpoint of Convex that says anything useful, so UpButler does not probe it. To check your own Convex account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Convex components
8 operational
Development Services
- Free & StarterOperational
- ProfessionalOperational
- BusinessOperational
Live Traffic
- Free & StarterOperational
- ProfessionalOperational
- BusinessOperational
- convex.dev websiteOperational
- AI GatewayOperational
Convex incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10, 2 of them rated major or critical by Convex.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Failing function calls | major | 36 min | |
| AI gateway unavailable | critical | 1 h 4 min |
Tell your outage from Convex's
Declare that your project depends on Convex. When one of your monitors fails while Convex has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- convexcurl -s https://upbutler.com/status/convex/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "convex",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Convex down right now?
- No. As of 2026-10-10 05:13 UTC, Convex is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Convex's own status page API at https://status.convex.dev. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Convex's words.
- How can my agent or app check Convex status?
- Fetch https://upbutler.com/status/convex/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"convex"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Convex's?
- Add "convex" to the dependencies of your UpButler workspace. When one of your monitors fails while Convex has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in databases and data
UpButler is not affiliated with Convex. Status and incident text belong to Convex and are read from their public status source; the probe result is UpButler's own measurement.