Is Convex Down?

No — Convex is up

Convex's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 274 ms

Right now

The verdict is the worse of these two. How we decide

Convex's status page

status.convex.dev · read 4 minutes ago · checked every 3 minutes

Operational

Convex's components, as its status page reports them
Component	Status
Free & Starter	Operational
Professional	Operational
Business	Operational
Free & Starter	Operational
Professional	Operational
Business	Operational
convex.dev website	Operational
AI Gateway	Operational

Open their status page

FlareWarden checks

convex.dev from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 274 ms
Checked: 3 hours ago

By region

Ashburn reachable, 117 ms
Dallas reachable, 332 ms
Frankfurt reachable, 124 ms
Johannesburg reachable, 613 ms
Los Angeles reachable, 219 ms
Newark reachable, 268 ms
Paris reachable, 176 ms
São Paulo reachable, 349 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	33 ms	3 ms	7 ms	106 ms
Dallas	186 ms	1 ms	55 ms	304 ms
Frankfurt	67 ms	3 ms	8 ms	113 ms
Johannesburg	455 ms	1 ms	63 ms	581 ms
Los Angeles	120 ms	2 ms	31 ms	204 ms
Newark	186 ms	2 ms	20 ms	255 ms
Paris	51 ms	10 ms	19 ms	136 ms
São Paulo	283 ms	1 ms	12 ms	338 ms

We check that convex.dev loads, not every feature behind it. Test it yourself

History

Incidents Convex reported

Since Oct 27, 10 days · from status.convex.dev

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Convex website availability

Measured by FlareWarden · convex.dev

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 252ms

Last 30 days

10-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of convex.dev from multiple regions every 6 hours. Convex's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 10 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Convex does

Convex is a reactive backend platform for developers writing TypeScript: a database, server functions, scheduled workflows, file storage, search and an AI Gateway for calling language models. Apps connect to their deployment at a convex.cloud address over a WebSocket, and query results update live as data changes. Apps built on Convex keep their data and logic there, so a Convex outage stops them from loading or saving data.

What an outage looks like

Apps built on Convex show errors from queries, mutations or actions, live data stops updating, or HTTP actions at a deployment's convex.site address fail or return 404. The dashboard shows 'Something seems wrong. The dashboard will attempt to reconnect automatically.' Convex's status page lists Live Traffic (running apps) and Development Services (dashboard, projects, accounts) per plan tier, with separate rows for the AI Gateway and the convex.dev website.

What to do about it

Check status.convex.dev and see whether Live Traffic or only Development Services is affected: Convex says development services can fail without affecting customer backends. Convex React retries mutations until they are written and runs each one only once, but actions are not retried automatically. A push that failed during an incident can be retried once it is resolved. Support questions go to the Convex Discord or support@convex.dev.

Is it down for everyone, or just you?

If this page says Convex is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Supabase

Firebase

AWS

Clerk

Convex outage FAQ

Does a Convex outage take my app down?

Only when Live Traffic is affected. On April 21, 2026 load issues hit Convex's sign-in, dashboard and deployment services while, Convex said, application live traffic was unaffected, and on September 18, 2026 dashboard logins failed with live deployments unaffected. Running apps do go down in Live Traffic incidents: on October 9, 2026 some query and mutation executions in us-east-1 failed from 22:11 to 22:52 UTC.

Will I lose data or users' edits during a Convex outage?

Stored data should be safe. Convex's docs say database state is replicated across multiple availability zones and that a physical outage may affect a deployment's availability but not the durability of its data. Convex React retries mutations until they are written, runs each only once and warns users who close a tab with mutations outstanding. Actions are not retried, so failed calls to outside services need your own retry.

Does an AWS outage affect Convex?

It has. On May 8, 2026 Convex reported intermittent downtime from an AWS Availability Zone issue: some customers saw more errors or extended downtime while workloads moved to healthy hardware and databases failed over, and Convex moved the affected infrastructure out of that zone. The incident lasted about one hour and fifty minutes. The October 9, 2026 us-east-1 failures were blamed on a network issue at an upstream provider.

Why do my HTTP actions fail when queries still work?

HTTP actions have broken on their own. On May 22, 2026 a Convex change broke HTTP actions on some deployments for about four hours, and until Convex repaired them automatically the fix was to redeploy with npx convex deploy. On August 12, 2026 HTTP actions reached through a proxy or CDN returned 404 from 00:20 to 04:15 UTC, because Convex's edge read the X-Forwarded-Host header and looked up the wrong deployment.

What does the check on this page measure?

It loads www.convex.dev, Convex's company website, which its status page tracks as the convex.dev website row. It does not connect to a deployment at convex.cloud, call an HTTP action at convex.site, sign in to the dashboard, push code or use the AI Gateway. A green result means the website answers, not that Convex backends are serving apps.

How we measure this

We request Convex's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Convex publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Convex itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Convex goes down

We check Convex every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required