status
briven, live.
probes run when this page is rendered — no cached numbers, no marketing dashboards. for incident history and post-mortems, see the full status page on docs.
every briven server & domain is guarded around the clock by web down — our independent uptime watchdog.
what if sign-in feels broken?
- check
redisunder the api probe above — rate limits need it healthy; logins can still work if only cache is down. - already-open sessions usually keep working; new sign-ups / magic links need the mail path.
- we post short incident notes here and on docs status when something is customer-visible.
incident in progress
checked at 2026-09-28T12:45:26.758Z · ttl 0s
api
control plane — accounts, projects, billing, deploy intake
ok200 · 19ms
- control_postgresok
- data_plane_postgresok
- runtimeok
- redisok
realtime
reactive query websocket service
ok200 · 38ms
web
marketing site + signed-in dashboard
down— · 7ms
fetch failed
docs
developer docs + sdk reference
ok200 · 45ms
probes timeout at 3000ms. /ready returns the service's view of its dependencies; /health only confirms the process is alive.