Operational Status

Service status and readiness

Live operational state for dashboard readiness, bot runtime health, and billing synchronization. Use this page to quickly understand whether an issue is local to your guild or platform-wide.

Last updated: Mon, Mar 9, 2026 2:00 PM Stale after: Mon, Mar 9, 2026 2:02 PM Snapshot Fresh

Dashboard

Operational

3/3 readiness checks healthy.

Bot Runtime

Degraded

Bot runtime is reachable with 0 failing health checks.

Billing Sync

Monitoring

No recent billing webhook activity detected in the last 24 hours.

24h uptime

0.00%

Last 24 hours

Incidents: 0 · Degraded days: 1

7d uptime

0.00%

Last 7 days

Incidents: 0 · Degraded days: 2

30d uptime

0.00%

Last 30 days

Incidents: 0 · Degraded days: 2

How to read this page

Status states summarize live checks with bounded probe timeouts and cached snapshots. Operational means healthy checks, monitoring means partial signal or low confidence, and degraded means active failures or unreachable dependencies.

Operational Monitoring Degraded

Update Cadence

Snapshot generated: 0 seconds ago
Stale threshold: 1 minute from now
Current freshness: Fresh

Incident communications

Some services are degraded. Check support channels for incident updates.

Support Channels Security Standards

What to do when status is degraded

Step 1

Check whether degradation is in Dashboard, Bot Runtime, or Billing Sync.

Step 2

Pause non-critical configuration changes until status returns to operational.

Step 3

Follow incident updates and use Support if your guild needs immediate assistance.

Incident timeline

Recent incident records and their current state.

No incident history is available in this window.

Status subscriptions

Subscribe to updates so your operators get notified when status changes.

Subscribe by Email Subscribe via Support Read Incident Playbook