Skip to content
Tutorials

Publishing Status Incidents

Report incidents and planned maintenance on GearCheck's public status page, and see what each post changes before it goes out.

GearCheck Operators
Who uses it
GearCheck super admins
Where it lives
Account menu > Staff > Status
Goal
Members and staff see accurate, current status on the public status page, in the banner at the top of GearCheck, and in the status notice on gear check replies when the bot is affected.
On This Page5 sections

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 happening: which services, how severe, and whether it's broken now or planned work with a start time.

Steps

  1. Create the incident

    Choose Incident or Maintenance. Add a title, pick a phase and, for an incident, an impact (Degraded, Partial outage or Major outage), then choose the affected services. Maintenance also needs a start time.

  2. Publish it

    Publish opens a confirm that lists the effects: what shows on /status, whether the banner and the bot notice start, and that a summary posts in #status-updates. Read it, then confirm. Upcoming maintenance changes nothing until its start time.

  3. Update it as it develops

    Post an update to move the phase or change the impact as you learn more. Each update opens the same confirm and posts again in #status-updates. While an incident affects the bot, gear check replies start with a status notice.

  4. Resolve it

    Resolve an incident, or mark maintenance completed, once the issue is over. /status moves it to Resolved and the banner and the bot notice stop. Reopen brings a resolved incident back. Retract removes one posted in error, and only the All tab shows it afterwards.

Check It Worked

  • The public status page at gearcheck.gg/status shows the incident with the right phase and impact, or the planned work under Upcoming.
  • 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-updates channel received the post.
  • Finished incidents are marked Resolved and finished maintenance Completed, and the banner is gone.

Common Pitfalls

  • Leaving an incident open after the issue is fixed, so the banner and the bot notice keep warning members for no reason.
  • Marking every incident as affecting all public services when only one service is actually down.
  • Retracting an incident that really happened. Retract is for posts made in error: it leaves /status at once, while earlier posts stay in Discord.