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 8 ms
Operational100.00% / 100.00%measured for 21.5% of the window
API — request handlingresponded in 11 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Background jobsresponded in 16 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Sessions and cacheresponded in 13 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Inside the API
Accounts and sign-inresponded in 15 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Servers and workspacesresponded in 14 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Server managementresponded in 17 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Billing and subscriptionsresponded in 15 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Internal toolsresponded in 13 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Support ticketsresponded in 15 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Infrastructure
uptime · 24h / 30dWhere players are routed to their server, and where server backups are written.
Backup storageresponded in 42 ms
Operational100.00% / 99.94%measured for 19.3% of the window
Server routingresponded in 23 ms
Operational100.00% / 99.98%measured for 19.3% of the window
Websites
uptime · 24h / 30dThe pages you use to sign in, manage servers and read about the service.
Admin panelresponded in 286 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Customer portalresponded in 240 ms
Operational100.00% / 100.00%measured for 21.5% of the window
eytak.comresponded in 26 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Game 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 20 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Falkenstein — noderesponded in 21 ms
Operational100.00% / 100.00%measured for 21.5% of the window
Madrid — player connectionsresponded in 39 ms
Operational99.86% / 99.96%measured for 21.5% of the window
Madrid — noderesponded in 27 ms
Operational99.86% / 99.96%measured for 21.5% of the window
Uptime 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.