Dexter

Partial outage

Live. Updated

A bot stopped checking in

InvestigatingSpark, Warden, Sentinel, Steward, Music botssince 4 days 12 h

Investigating · A bot stopped checking in. The team has been alerted.

Systems

  1. Spark

    Economy, games, levels and giveaways

    Status
    Down
    Latency
    143 ms
    Uptime 90 days
    99.73%

    A bot stopped checking in

  2. Warden

    Moderation, cases and tags

    Status
    Down
    Latency
    49 ms
    Uptime 90 days
    99.73%

    A bot stopped checking in

  3. Sentinel

    Automod, raid protection and logging

    Status
    Down
    Latency
    47 ms
    Uptime 90 days
    99.73%

    A bot stopped checking in

  4. Steward

    Modmail, tickets and the help desk

    Status
    Down
    Latency
    55 ms
    Uptime 90 days
    99.71%

    A bot stopped checking in

  5. Music bots

    Music in voice channels: /play, /music and /playlist

    Status
    Down
    Latency
    39 ms
    Uptime 90 days
    99.65%

    A bot stopped checking in

  6. Website & dashboard

    dexterai.dev, the guide and the dashboard

    Status
    Operational
    Latency
    2 ms
    Uptime 90 days
    99.97%
  7. Database

    The data every bot shares

    Status
    Operational
    Latency
    0 ms
    Uptime 90 days
    100%
  • No problems
  • Some downtime or slow replies
  • Down more than 5%
  • No data

Metrics

The last 90 days, from the bots’ own measurements.

Latency

How fast the bots reach Discord and answer you.

Gateway latency ms

How long Discord’s gateway takes to answer each bot’s heartbeat.

Loading the chart…

Discord API round trip ms

One authenticated Discord API request, timed every minute.

Loading the chart…

Reply time to commands and buttons ms

The slowest 1% of first replies, worst in each day. Discord gives up at 3,000 ms.

Loading the chart…

Traffic

What the bots handle.

Commands and buttons /min

Slash commands, buttons and menus handled, per minute.

Loading the chart…

Messages processed /min

Server messages each bot received, per minute.

Loading the chart…

Discord API calls /min

Requests each bot sent to Discord’s API, per minute.

Loading the chart…

Stability

Reconnects, rate limits and late replies. Lower is better.

Gateway reconnects

Times a bot resumed or re-opened its gateway connection, per day.

Loading the chart…

Rate limits hit

Discord API requests that had to wait for a rate limit, per day.

Loading the chart…

Slow or missed replies

Replies that took over 2 seconds or missed Discord’s 3-second window, per day.

Loading the chart…

Resources

Processor and memory per bot.

CPU %

Processor time each bot used, as a share of one core.

Loading the chart…

Memory MB

Memory each bot process holds (resident set).

Loading the chart…

Website

Website response time ms

A request to the website and dashboard, made every minute from the bots’ host.

Loading the chart…

Database

Database query time ms

A one-row query from each bot, every minute: typical and slowest.

Loading the chart…

Incident history

The last 90 days.

  1. Spark stopped checking in

    ResolvedSpark to 5 minutes

    Resolved after 5 minutes.

  1. A bot stopped checking in

    InvestigatingSpark, Warden, Sentinel, Steward, Music botssince 4 days 12 h

    A bot stopped checking in. The team has been alerted.

  1. Spark stopped checking in

    ResolvedSpark to 5 minutes

    Resolved after 5 minutes.

  1. The website is not answering

    ResolvedWebsite & dashboard to 10 minutes

    Resolved after 10 minutes.

  2. The bots’ host is down

    ResolvedSpark, Warden, Sentinel, Steward, Music bots, Website & dashboard, Database to 15 minutes

    Resolved after 15 minutes.

  3. Spark was unavailable

    ResolvedSpark to 16 minutes

    Spark is back and working normally. It was unavailable for 16 minutes.

  4. Steward was unavailable

    ResolvedSteward to 16 minutes

    Steward is back and working normally. It was unavailable for 16 minutes.

  5. Sentinel was unavailable

    ResolvedSentinel to 16 minutes

    Sentinel is back and working normally. It was unavailable for 16 minutes.

  6. Warden was unavailable

    ResolvedWarden to 16 minutes

    Warden is back and working normally. It was unavailable for 16 minutes.

  7. Music bots was unavailable

    ResolvedMusic bots to 16 minutes

    Music bots is back and working normally. It was unavailable for 16 minutes.

  8. The bots’ host is down

    ResolvedSpark, Warden, Sentinel, Steward, Music bots, Website & dashboard, Database to 5 minutes

    Resolved after 5 minutes.

  9. Spark was unavailable

    ResolvedSpark to 8 minutes

    Spark is back and working normally. It was unavailable for 8 minutes.

  10. Warden was unavailable

    ResolvedWarden to 8 minutes

    Warden is back and working normally. It was unavailable for 8 minutes.

  11. Steward was unavailable

    ResolvedSteward to 8 minutes

    Steward is back and working normally. It was unavailable for 8 minutes.

  12. Sentinel was unavailable

    ResolvedSentinel to 8 minutes

    Sentinel is back and working normally. It was unavailable for 8 minutes.

  13. Music bots was unavailable

    ResolvedMusic bots to 8 minutes

    Music bots is back and working normally. It was unavailable for 8 minutes.

  14. Spark stopped checking in

    ResolvedSpark to 5 minutes

    Resolved after 5 minutes.

  15. Steward was unavailable

    ResolvedSteward to 1 hour 2 min

    Steward is back and working normally. It was unavailable for 1 hour 2 min.

  16. Sentinel was unavailable

    ResolvedSentinel to 1 hour 2 min

    Sentinel is back and working normally. It was unavailable for 1 hour 2 min.

  17. Warden was unavailable

    ResolvedWarden to 1 hour 2 min

    Warden is back and working normally. It was unavailable for 1 hour 2 min.

  18. Music bots was unavailable

    ResolvedMusic bots to 1 hour 2 min

    Music bots is back and working normally. It was unavailable for 1 hour 2 min.

  19. Spark was unavailable

    ResolvedSpark to 1 hour 2 min

    Spark is back and working normally. It was unavailable for 1 hour 2 min.

  20. Spark stopped checking in

    ResolvedSpark to 5 minutes

    Resolved after 5 minutes.

  21. The website is not answering

    ResolvedWebsite & dashboard to 5 minutes

    Resolved after 5 minutes.

  22. Spark stopped checking in

    ResolvedSpark to 5 minutes

    Resolved after 5 minutes.

All 58 incidents