Why our status page doesn't live on our own infrastructure
21 août 2026
Plenty of hosts display a "99.9% uptime" badge on their homepage. The problem: if that badge is hosted on the same server it's supposed to monitor, it goes down right along with it. An outage would then never be visible — the badge would keep saying "all good" right up until nobody could even view it anymore.
The principle: monitor from the outside
Our status page (statusmc.rmdc.cloud) deliberately runs on a machine that's completely independent from our game infrastructure, at a different provider. That's not a minor technical detail — it's what gives the page any real meaning. If our game infrastructure runs into trouble, the status page shows it — it can't go down with it, since it shares no dependency with it whatsoever.
What that actually changes
The history shown is a real, regularly measured history from the outside, not a statement we choose to display or hide. If an incident happens, it stays visible in the history — even after it's resolved. That's more demanding for us: no erasing a bad measurement. It's also the only approach that makes sense: a status page that can never show red conveys no information at all — it just reassures for nothing.
Put to the test
We regularly test this independence by simulating outages of our own game infrastructure, to verify that the status page keeps working and correctly reflects the incident while it lasts. Same principle as what's detailed on ourinfrastructure page: verifiable guarantees, not numbers displayed with nothing behind them.
This isn't a marketing feature. It's the minimum condition for a status page to actually mean anything.