Every shard, right now.
Arclo runs sharded across clusters. Each row below is one gateway connection, reporting its own state. Read live, not summarised after the fact.
All shards operationalShards
A shard that stops writing its row is marked not reporting rather than left showing its last good state.
| Shard | Status | Servers | Members | Ping | Uptime | Cluster |
|---|---|---|---|---|---|---|
| #1 | Ready | 990 | 78,646 | 18 ms | 2d 5h | 1 |
| #2 | Ready | 956 | 108,441 | 16 ms | 2d 5h | 1 |
| #3 | Ready | 974 | 48,331 | 27 ms | 2d 5h | 1 |
Find your server’s shard
Paste your server ID. The answer is worked out in your browser and never leaves it.
Discord assigns shards by (server_id >> 22) % 3 (counted from zero; the table above counts from one), so the answer depends on when your server was created, and it changes whenever the shard total does.
What a shard is
Discord splits a large bot’s servers across several gateway connections. Each one is a shard, several shards share a cluster process, and a shard going down affects only the servers on it, which is why this page lists them separately rather than as one green tick.
Give your server its weekend back.
One all-in-one bot, 50+ systems, one dashboard, one login. Add Arclo and have your first system running before you finish this sentence.