Availability and Maintenance Windows
Mirox runs in two independent regions. Each region carries the complete platform, and traffic is routed to a healthy region automatically. Behind that, every service is built to keep answering during a disruption instead of disappearing, and the app tells you plainly what is going on.
What you see during a disruption
Every answer the platform gives carries a status. The web app and the mobile app read it and react the same way:
| Status | Meaning | What the app shows |
|---|---|---|
healthy | Everything works. | Nothing special. |
degraded | A non-essential part is unavailable; the app still works. | Nothing special; affected functions report an error when used. |
unavailable | The platform cannot serve requests right now (for example the database is unreachable). | A full-page notice replaces the app as soon as a request fails. The page checks the platform every few seconds and returns to the app by itself once it works again. |
maintenance | A maintenance window is active. | While the platform still works: a yellow notice at the bottom right with the window's title and time span. It can be collapsed to a small warning icon and opened again. If requests start failing inside the window, the full-page notice appears with the same information. |
The full-page notice shows the window's title, description and time span when they are known, and a general notice otherwise. Language and dark mode can be switched on that page as on the login page. Nothing has to be reloaded manually.
Your plants keep running
Every plant has its own Mirox agent. The agents run decentralised on dedicated agent clusters in regions separate from the platform itself, so a regional problem on the platform side does not affect them. An agent does not depend on the platform being reachable:
- The agent keeps collecting and analysing the plant's data and keeps it in a local buffer while the platform is unavailable; the buffered data is delivered once the connection is back, so the history has no gap.
- The management of the agents treats a platform disruption as exactly that: the plant workloads stay deployed and running. They are never stopped because the cloud is temporarily unreachable or in maintenance.
- Alarms that the agent evaluates itself continue to be evaluated; notifications that go out through the platform follow as soon as it is available again.
Maintenance windows
The Mirox team announces planned work as a maintenance window. A window has a title, a short reason shown to users, a planned start and end, and a scope: the whole platform or one region.
- Before the start the window is announced at least five working days in advance. Windows are scheduled only when work requires one, not on a weekly rhythm, and normally on a Saturday between 20:00 and 23:59 Central European Time. The app shows nothing before the window starts.
- During the window the yellow notice appears, and the platform may be briefly unavailable. The agents continue to work as described above.
- After the end the notice disappears by itself. If the work finishes early, the window is ended early; if it takes longer, it is extended and the notice stays.
A window never changes your data or your configuration. It only tells the app, the agents and the platform's own services that interruptions in that period are expected.
For integrations and API users
If you call the Mirox API from your own systems, use the status to react correctly:
- Every HTTP response carries the header
X-Mirox-Statuswith one of the four values above. GET /status(no authentication required) returns the current state and, during a window, its title and time span.- A
503together withunavailableormaintenanceis a platform condition, not a problem with your request or your credentials. Retry later with a growing pause instead of immediately. Authentication errors (401,403) are unrelated to this mechanism and should not be retried blindly.
Frequently asked questions
Why do I see a maintenance notice although everything works? The window is active, so interruptions are possible. The notice is informational; you can collapse it.
Is my plant data lost during a disruption? No. The agent buffers it and delivers it afterwards.
Can I be informed before a window? Yes. Planned windows are announced at least five working days in advance through the usual channels; the app itself shows a window only while it is active.