/shardinfo

This command allows you to view all the active shards (virtual subdivisions of our VPS) and their usefull informations.

This command is up to date and currently works without known issues.

---

EXECUTION:

/shardinfo

No additional fields needed.

---

USEFULL INFORMATIONS:

The first result you will get when you execute your command is a string like this:

Il tuo server è nello shard (NUMERO)

With this report, you can check in what shard your server it's in currently, and you can then cross the informations with the shards status informations.

Warning! Shard assignment is not done statically; Your server shard could change frequently due to optimizzation system that equilibrates our shard workload.

---

SHARD STATUS AND INFOS:

When executing the command, you will receive a list of shards aswell. You have find the shard numbers you are looking for (like the shard where your server is in) and read all the informations.

Here's a full list of all the informations you can extract by the shard analisys.

• Shard name and code

• Number of servers the shard is hosting

• Number of all users managed within the Shard

• Ping (ms)

• Uptime (date)

When checking the Shard Informations you can find a circle near the shard name and code. The circle can assume three different colours such as green, yellow and red.

The circles shows the current status of the shard:

• Green circle [🟢] means that the shard ping is optimal (lower than 200ms)

• Yellow circle [🟡] means that the shard ping is abnormal (200-500ms)

• Red circle [🔴] means that the shard ping is critical (more than 500ms)

The PING is the time in milliseconds that the bot takes to receive and process a command.

This could be influenced by database query (in compex commands and calculations) and by Discord API latency that is crucial for the bot responsivity.

If our ping is very high and the shard is in critical status you can continue using out bot without any major problems. Be aware that the bot could take longer to respond or that the interaction could fail (if this happens just exeute the command again until it works).