Check whether an ED5 service — the editor, play client, Copilot, media or the managed server fleet — is having a problem before you debug your own game.
ED5 Platform Status
The public status page at /status on the ED5 MMO Studio website (linked as Platform Status in the site footer) shows the live health of the services every hosted project depends on. Check it first when something that normally works suddenly doesn't — if a platform service is down, the fix is ours, not yours.
This is different from Studio → Status, which shows your own game server (see Reading the Server Status Page).
What It Shows#
| Component | What it covers |
|---|---|
| Website & accounts | This site, sign-in, the studio dashboard and billing |
| Studio Web editor | The browser editor for hosted projects |
| Play client | The browser game client your players join through |
| AI Copilot | The assistant inside the editor |
| Media CDN | Delivery of hosted sprites, tiles, audio and cover images |
| Managed game servers | The hosted server fleet as a whole — counts only, never individual projects |
States#
| State | Meaning |
|---|---|
| Operational | Answering normally |
| Degraded | Working but slow, returning some errors, or a share of the fleet is impaired |
| Outage | Not answering, or many managed servers are unreachable at once |
| Maintenance | Planned work is in progress |
| Not monitored | That service is not checked from this site |
Each service is checked about once a minute, and the page refreshes itself while it is open. The time of the last check is shown under the title.
Incidents#
When we are working on a problem, it is posted under Active incidents with its impact (minor, major, critical or maintenance), the affected services, and a timeline of updates. Resolved incidents stay under Past incidents for 14 days. Planned maintenance is listed ahead of time and only counts against a service once its window starts.
For Monitoring Tools#
The same data is available as JSON at /api/status — point an uptime monitor or a team dashboard at it. It contains service states and fleet counts only; no addresses, project names or player data.
Gotchas#
- The fleet line is the platform, not your server. One project's server failing (for example, a content error at boot) does not turn the fleet amber. Your own server's health is on its project page in your dashboard and in Studio → Status.
- "Not monitored" is not an outage. It means that service has no health check configured from this site.
- Numbers can lag by up to a minute. Results are cached for 60 seconds so the checks never add load during an incident.