Loading
Whether everything is working, what broke recently, and what players are telling us right now.
Something important is down and we are on it.
Checked just now
Website
The arcade itself - browsing games, profiles and every page on the site.
Accounts and sign-in
Signing in, signing up, and linking Discord or Google.
Games and scoresSet by staff
Loading a game, playing it, and having the run recorded.
Leaderboards
Rankings, personal bests and the podium.
Parties and multiplayer
Party rooms, invites and real-time match state.
Messages and friends
Direct messages, group chats, friends and stories.
Credits and shop
Credit balances, the shop, the inventory and cosmetics.
Database
The Supabase Postgres instance everything above is built on.
Discord botSet by staff
Slash commands, the gateway worker, chat levels and the live feed.
Fixing issues.
Discord API
Discord itself. Shown because our bot is only ever as up as Discord is.
Reports are at their normal level. Nothing in the last hour.
Everything on this page is available as JSON, with CORS open to anyone and no key required. Add to the summary for a Statuspage-compatible document that existing tools already understand.
0
0
0
0 reports in the last 24 hours. Reports come from players and are counted, not verified - they point us at problems our own checks have missed.
?format=statuspageGET/api/status
Everything: components, incidents, maintenance, report signal.
GET/api/status/components
Just the components and their current status.
GET/api/status/components/{slug}
One component, with 90 days of uptime.
GET/api/status/incidents
Incident history. `?active=1` for open ones only.
GET/api/status/uptime?component={slug}
Daily uptime series for a component.
GET/api/status/reports
Player reports as 15-minute buckets, with the baseline.
POST/api/status/reports
Submit a report. Rate limited per connection.
GET/api/status/badge?component={slug}
An SVG badge to embed anywhere.
The Discord bot reads the same endpoints - try /status in the server.
0
7
3
26
0