Major impactResolvedDatabases

Convex outage: Some custom domains not working

Convex reported this major-impact incident on its official status page on Feb 10, 2026, 01:26 UTC. It was resolved after 35 min.

Right now Convex is operational. Live Convex status →

🔔 Get alerted when Convex has issuesFree · email alerts · no credit card
Feb 10, 2026, 01:26 UTC
started
Feb 10, 2026, 02:01 UTC
resolved
35 min
duration
Major
impact

Affected components

  • Free & Starter

Timeline

updates from Convex's status page ↗
  1. resolvedFeb 10, 2026, 02:01 UTC

    This incident has been resolved.

  2. monitoringFeb 10, 2026, 01:31 UTC

    All hostnames have been reconfigured and should be available again.

  3. identifiedFeb 10, 2026, 01:26 UTC

    A misconfiguration caused many custom domains to stop working with a TLS error. We are rolling out a fix.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Convex's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Convex have incidents?

Convex reported 5 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 57 min. See Convex's uptime and incident history

← Previous: Convex Dashboard Availability (Feb 7, 2026)Next: high error rates on customer backends (Mar 4, 2026) →
Convex outage on Feb 10, 2026: Some custom domains not working · APIStatus.watch