Status

Is Relay working?

• Discord connection—
• Tickets and moderation—
• Timers and scheduled jobs—
• Dashboard and API—

Rechecked every 30 seconds. Check now

Incidents

Anything longer than a blip — an outage, a Discord incident that affects Relay, or planned maintenance — is posted in #status in the Relay Discord, with what it affects and when it's resolved. There's nothing open right now that isn't shown above.

If something looks wrong

Relay being up doesn't always mean it's working in your server. In order:

1. Check the boxes above. If the Discord connection is down, it's us — nothing you change will help, and it'll come back on its own.
2. Run /setup again. It repairs a deleted channel, a missing tag or a broken webhook, and it never deletes anything.
3. Check Relay's permissions. If it's missing one, Relay says which when it fails. Grant it to Relay's role, or re-invite from the front page.
4. Check Discord itself at discordstatus.com — an API incident there looks a lot like a Relay one.
5. Still stuck? Ask in the Discord or email support@getrelaybot.com. Server name, what you expected, what happened, and roughly when.

What the checks mean

Discord connection

Relay's gateway session. Down means Relay can't see or send anything, anywhere.

Tickets and moderation

The database behind every ticket, report and case, with how long a trivial query took. Down means new tickets can't be opened.

Timers and scheduled jobs

Auto-close, SLA reminders, temporary bans and the weekly summary. Degraded means they're running late, not that they've been lost — the queue is in the database and picks up where it left off.

Dashboard and API

getrelaybot.com/dashboard and the API behind it. You're reading this from it, so if the page loaded, it's up.

Monitoring this yourself? GET /health returns the same numbers as JSON, and answers 503 when Relay is down.