Status
All systems operational
Checked . Each GPU pool is health-checked at most every 30 seconds; reload for the latest result.
Components
Each part, checked live
Each GPU pool is probed at most every 30 seconds. A moving pulse means the component answered; a flat red row means it did not.
API gateway (Cloudflare edge)
Global edge
Operational:Serving
Primary GPU pool
Switzerland
Operational:Ready · 383 ms probe
Cloud GPU pool (autoscaling)
European Union
Operational:Ready · 209 ms probe
Routing mode: auto. Requests fail over between GPU pools automatically; a pool being down only reduces redundancy. Probe times are one round trip from our server to each pool, measured at the last check.
Failover
How failover and Swiss-only mode work
Two rules decide where a request is answered. Here is what happens when a pool has a bad minute.
- Default: fail over, keep answering. Requests go to the primary pool in Switzerland first. If it is saturated or unhealthy, the gateway retries on the autoscaling cloud pool, so the answer still arrives. Every response names where it was processed in the x-laya-region header.
- Swiss-only mode: never leave the country. One switch per workspace (or the x-laya-residency: ch header per request) and requests are only ever answered in Switzerland. If the Swiss pool is unavailable you get an error, never a silent detour abroad. Switching it on applies to keys already in use within about 5 seconds. It is an add-on: +15% credits per request, still below Jev.