Web Chat sign-in
ReachableThe Web Chat front door is reachable.
152ms · HTTP 307
Running service checks…
System status
Components
Web Chat sign-in
Studio sign-in
API
Dashboard and pricing
Documentation
Public website
Running service checks…
System status
Web Chat sign-in
Studio sign-in
API
Dashboard and pricing
Documentation
Public website
System status
Public reachability, API dependencies, authenticated inference, and commerce/webhook processing are checked separately so a green front door cannot hide a broken request path. A monitor marked “Setup needed” is disclosed rather than reported as a passing end-to-end check.
The Web Chat front door is reachable.
152ms · HTTP 307
The Studio front door is reachable.
83ms · HTTP 307
Database, routing, and shared rate limiting report ready.
169ms · HTTP 200
A cached one-token request verifies authentication and an end-to-end model route when the dedicated status key is configured.
172ms · HTTP 200
Payment schema, enabled checkouts, stalled fulfillment, and active-provider webhook processing are checked without exposing transaction data.
272ms · HTTP 503
Usage lookup and pricing are reachable.
264ms · HTTP 200
The public model and pricing catalog is reachable without signing in.
367ms · HTTP 200
The public support form is reachable without signing in.
365ms · HTTP 200
Documentation is reachable.
363ms · HTTP 200
The main CloudService website is reachable.
377ms · HTTP 200
Checks are cached briefly and show current state, not a contractual uptime percentage. The inference check uses a dedicated key only when configured; payment health exposes aggregate state, never credentials or transaction details. If a component is unavailable, wait before retrying or contact support.
No verified incident updates are currently listed
Incident reporting is active. Only verified incident updates are listed; the absence of an entry is not an uptime guarantee.