Documentation
Back to tutorials

Operations

Publishing Status Incidents

Create and update the incidents that show on GearCheck's public status page and warn users when something's degraded.

Who uses it

GearCheck super admins

Where it lives

Dashboard > Moderation > Status Incidents

Goal

Members and staff see accurate, current status information, both on the public status page and as a warning inside gear check flows when something's affected.

Before You Start

  • Super admin access. This page is for GearCheck's own platform staff, not guild-level moderators.
  • A clear read on what's affected: which service, how severe, and whether it's ongoing or scheduled maintenance.

Steps

1

Create the incident

Fill in a title, pick a status (Investigating, Identified, Monitoring, Scheduled maintenance, or Resolved) and a severity (Degraded, Partial outage, Major outage, or Maintenance), then choose which services are affected.

2

Publish it

Publishing writes the incident to the public status page right away and mirrors a summary to the support Discord's status channel, so members and staff see the same information in both places.

3

Update it as it develops

Edit the incident to change its status or severity as you learn more. Each update mirrors to the support Discord again, so the history stays visible there too. While an incident is active, GearCheck also shows a short warning inside gear check flows for the services it affects.

4

Resolve it

Use Resolve once the issue is over. A resolved incident stops counting as active, so it no longer shows on the public status page as ongoing or triggers the in-flow warning.

Launch Checklist

  • The public status page at gearcheck.gg/status shows the incident with the right status and severity.
  • Affected services are accurate. An incident scoped to all public services shows up everywhere, so narrow it when you can.
  • The support Discord's status channel received the mirrored update.
  • Resolved incidents are actually marked Resolved, not just left on an old status.

Common Pitfalls

  • Leaving an incident open after the issue is fixed, so it keeps warning members during gear checks for no reason.
  • Marking every incident as affecting all public services when only one service is actually down.
  • Mixing this up with a guild's Bot Status page. Guild-specific problems belong there, not on the public status page.

Related