Status · Karen

All systems operational

Postgres and Redis are both answering.

Health

Postgres

operational

28ms

Redis

operational

8ms

Discord gateway

operational

14ms

Derived from the bot’s last published snapshot, which expires after two minutes.

Dispatch queue

clear

Processed

In flight

Backlog

Failed

Retrying Jobs waiting out a backoff before another attempt. Three attempts, then the job is kept for inspection.: 0
Kept for inspection Exhausted jobs still on the queue. Capped at 500, so this is a sample of recent failures rather than a total.: 10

Dashboard dispatches only. A prefix command typed in Discord never enters this queue, and the backlog reads 0 whenever the bot is consuming jobs as fast as they arrive — which is the normal state, not an idle one. Processed and failed count from the worker’s last restart, not from install.

Footprint

as cached by the bot

Servers

Members

15k

Channels

1.5k

Latency

Last hour

29 samples

Service	p50	p95	max	coverage
Postgres	16ms	57ms	57ms	29/29
Redis	2ms	17ms	21ms	29/29
Discord gateway	16ms	16ms	16ms	29/29

Coverage is how many samples in the window recorded a reading. It is not uptime — a missing sample can mean the collector did not run.

Gateway distribution

29 readings

15msbars past p95 are the tail16ms

Reporting coverage

last hour

Postgres40/40

Redis40/40

Discord gateway40/40

A neutral notch means no sample was recorded in that slice. That can mean the service was down or that the collector did not run, and this page cannot tell those apart — so it is not drawn as an outage, and none of these rows is an uptime figure.

Runtime

Processes

since last restart

Gateway session: 48h 8m
Bot process: 48h 8m
Bot memory: 201.6 MiB
API process: 48h 8m

Restart ages, not availability. A deploy resets both, and neither figure can be read as an SLA.

Your connection

Round trip from this browser.

Snapshot age

The bot republishes stats on a two-minute expiry.

26s

Commands

Command activity

28 in 24h

-18h-12h-6hnow

Peak hour: 9. Columns are scaled against it, so the shape is relative to this window and not to any other day.

ranrefusederroredRefused covers a disabled command, a cooldown, or a missing permission.

Last 24 hours

79% ran

Outcome

Ran2279%

Missing permission14%

Rate limited00%

Disabled or gated00%

Errored518%

Source

Discord28100%

Dashboard00%

Execution timemedian 547ms, p95 1.9s

Mean time inside the command engine, per hour. Hours with nothing in them break the line rather than being drawn as zero.

Latency trends cover the last hour, sampled every 15 seconds; command activity covers the last day, bucketed by hour. Neither is uptime — Karen does not publish an availability figure, so none is shown here.