GearCheck status

Live checks of each GearCheck service, and the incidents the GearCheck team posts.

All services operational

Checked Nov 8, 8:35 PM UTC

All 9 checks passed. No active incidents.

Services

Web dashboardOperational
The status page itself loaded fine.
What depends on it
Public pages load. Signed-in dashboard pages also need the API and the database.
APIOperational
Last heartbeat under a minute ago.
What depends on it
Dashboard data, setup, billing, the marketplace and gear check history need the API.
Discord botOperational
Last heartbeat under a minute ago.
What depends on it
Slash commands, gear checks, role grants, DMs and Discord notifications need the bot.
DatabaseOperational
Connection check passed.
What depends on it
Settings, builds, sessions, billing state, audit logs and notifications live in the database.
Evidence processingOperational
Everything it needs is working.
What depends on it
Gear checks can fail, queue or come back incomplete when this is degraded.
NotificationsOperational
Everything it needs is working.
What depends on it
Discord delivery and reminders can be late. The web inbox still works while the API and database are up.
BillingOperational
Billing checks are passing.
What depends on it
Checkout, the billing portal and plan changes need billing and the database.
Discord APIOperational
No Discord API problem is recorded.
What depends on it
Server lookups, channels, roles, slash commands, DMs and message delivery need Discord.
RaidHelperOperational
RaidHelper health for each server is on its Bot Status page.
What depends on it
Readiness reports and event imports need GearCheck and RaidHelper, plus each server's RaidHelper key.

And Notifications, Billing, Discord API, and RaidHelper: Operational.

1The last 25 are kept here

Known Issue - OCR InconsistencyResolved
Partial outage
AffectsEvidence processing
Resolved May 8, 2:00 PM UTC

Services are separate. A problem can stop Discord commands while the dashboard still loads, or the other way round.
Problems in one server only (channel permissions, a RaidHelper key) show on that server's Bot Status page, not here.
If this page can't reach the API, it says so and marks what it couldn't check as Unknown.

Channel permissions, RaidHelper keys, screenshot reading settings and notification rules are checked per server on its Bot Status page.