The router read the session before putting Home up, and a failed read went to the error screen. Everything on Home but the sign-in panel — the headline, the pitch, the three facts, the footer — is in the bundle that was just served off S3 and asks the API for nothing, so an API outage was telling strangers the site was broken instead of what the site is. Home now takes a panel rather than a session, and the third state fills the sign-in form's place with the message and a Try again. Not the form with an error over it: whatever stopped /api/session will stop /api/login too, which was the error screen's reason and is the half worth keeping. Matches still gets the error screen, having nothing to show without the API.