Health
Routing status, first-party.
Every WinLEW service runs on one first-party domain — no subdomains, no third-party status host. Each route below is checked live, over loopback, on every page load — not a hardcoded claim.
Each bot reports in on its own. A light is only green because the bot said so — nothing here is inferred from the website being up.
Checked one level deeper than a page load — each must also report ok:true in its own response, not just HTTP 200.
Every page, game, and reward flow is served from winlew.co itself, so a link never depends on a separate host staying alive or its certificate staying valid.
Wallet selection, desktop-to-phone handoff, and Discord Linked Roles all run through /verify/ — one verification that the Dashboard, Quiz, Faucet, and Governance all read from.
Bot documentation, commands, and legal pages live under /discord-bots/, and the bots' own help commands link back to these same first-party routes.
- It reports whether these routes respond correctly right now, checked from the server over loopback each time you load it. It is not a historical uptime record — there is no stored history behind it, and it does not claim an uptime percentage.
- A red check means that route was failing at the moment you loaded this page. Reloading re-runs every check from scratch.
- Data APIs are held to a higher bar than pages: an API must also report success inside its own response body, so a route that returns HTTP 200 while its underlying lookup failed is still counted as unhealthy.