Skip to main content

lastplayed.io · System status

System status

All systems operational
This page is maintained by hand. Times are UTC.

Incident history

July 6, 2026

SEV-1Resolved~5 h impact
lastplayed.io /u/:username hydration failure — postgres driver (and Buffer) leaked into the client bundle
A four-line feature change made a helper function documented as \"pure, no server-only imports\" start importing the Postgres driver. Because that helper lives in a file the public profile route imports directly, the driver — and the Node-only `Buffer` global it depends on — shipped to every visitor's browser. The server kept returning HTTP 200 with a correct HTML shell the whole time; every public profile page (`lastplayed.io/u/:username`) simply never hydrated client-side for ~5 hours.

June 21, 2026

SEV-1Resolved~43 min impact
lastplayed.io 503 outage — image registry unreachable during a node fault
A fault on a single cluster node simultaneously killed lastplayed.io's app pods and the private image registry they needed to restart; the site returned 503 for ~43 minutes until it was served from a cached image. The user-facing outage is over; a durable node fix is still pending.