System Status
Every component below is checked from outside our platform, as often as once a minute. Uptime is the share of monitored time that was up — and any stretch we failed to measure is shown as a gap rather than counted in our favour.
API
uptime · 24h / 30dThe API every request passes through, and the three surfaces that can fail independently of it answering at all: request handling, background jobs and the session store. The services listed beneath run inside the API and fail independently of each other.
API — reachableresponded in 13 ms
Operational99.94% / 99.87%measured for 47.8% of the window
API — request handlingresponded in 10 ms
OperationalBackground jobsresponded in 60 ms
OperationalSessions and cacheresponded in 14 ms
OperationalInside the API
Accounts and sign-inresponded in 14 ms
OperationalServers and workspacesresponded in 12 ms
OperationalServer managementresponded in 17 ms
Operational100.00% / 98.43%measured for 58.7% of the window
Billing and subscriptionsresponded in 16 ms
OperationalInternal toolsresponded in 15 ms
OperationalSupport ticketsresponded in 13 ms
OperationalInfrastructure
uptime · 24h / 30dWhere players are routed to their server, and where server backups are written.
Backup storageresponded in 46 ms
Operational100.00% / 99.88%measured for 98.6% of the window
Server routingresponded in 21 ms
Operational100.00% / 99.99%measured for 98.6% of the window
Websites
uptime · 24h / 30dThe pages you use to sign in, manage servers and read about the service.
Admin panelresponded in 31 ms
OperationalAdmin proxyresponded in 17 ms
Operational100.00% / 99.98%measured for 57.4% of the window
Customer portalresponded in 78 ms
OperationalPortal proxyresponded in 11 ms
Operational99.95% / 99.99%measured for 57.4% of the window
eytak.comresponded in 25 ms
OperationalGame regions
uptime · 24h / 30dOne row per region that exists. Player connections is a real Minecraft connection to the region's edge router; node is the machine your server runs on.
Falkenstein — player connectionsresponded in 13 ms
OperationalFalkenstein — noderesponded in 13 ms
OperationalMadrid — player connectionsresponded in 239 ms
OperationalMadrid — noderesponded in 26 ms
OperationalUptime is calculated from checks recorded since 8 Aug, 18:07. A window with no data shows a dash rather than an estimate, one we watched only part of says how much of it we watched, and a day we hold no measurements for is left blank on the timeline. The monitor runs outside the platform it checks, so an outage of the monitor itself is a gap in this history rather than an incident in it.