Status page
Updated on October 27, 2026
Status page
The platform's real-time status, publicly accessible at /status. Check it first when something seems off.
What it shows
- Overall status and the status of each key component (API, deployments, registry, network...): operational, degraded, or down.
- Cluster servers: live availability and load.
- 30-day availability history: one bar per day and per component, with the availability percentage. Past incidents remain visible there.
- Ongoing and past incidents, with their resolution timeline.
- Scheduled maintenance, announced in advance with its time window.
How to use it
| Situation | Reflex |
|---|---|
| Your services seem slow or erroring | Check whether a component is degraded |
| Deployment not starting | Look at the build/registry component status |
| Planned interruption to schedule around | Check announced maintenance |
| Confirmed problem only on your side | Open a ticket |
An incident shown on the status page is already known to the team. There is no need to open a ticket to report it. The incident thread is updated until resolution.
Incident or local problem?
If the status page is green but your service is erroring, the cause is probably in the service itself: start with its logs and the AI diagnostic for the crash.