United Network Status
This page shows whether United is connected to Discord, how its gateway shards are distributed, and how many communities currently use the bot without publishing a server directory.
United shard network
Discord divides larger bot connections into gateway shards. Each card reports only an aggregate server count and gateway latency.
Find your server's shard
Paste a Discord guild ID to calculate its assigned United shard. The ID is processed only in your browser and is never submitted to United.
What these statistics mean
The server total is the number of Discord communities currently connected to the primary United bot. Join and leave totals describe bot additions and removals recorded during the last thirty days. They do not count individual Discord members joining or leaving a community. Gateway latency is reported per shard when Discord provides a usable measurement.
These figures are operational indicators, not a popularity ranking. A temporary Discord outage, a network restart, or a shard reconnect can briefly affect the values. United refreshes the public snapshot regularly, while the authenticated dashboard continues to use live server-specific data for owners.
What United keeps private
United does not publish a searchable server directory, server names, invite links, member lists, channel names, staff names, moderation records, or dashboard settings. The network page intentionally exposes only aggregate counts and technical shard health. Server owners see their own information only after Discord authorization.
The shard lookup is intentionally local. Discord guild IDs contain enough information to calculate a shard assignment with Discord's documented formula. The browser performs that calculation after it has loaded the current shard count. The entered ID is not included in the statistics request, stored by the page, or sent to an analytics endpoint.
How to use this page during troubleshooting
If United appears offline in one server, first check whether the network totals and shard cards load. A healthy public network does not prove that United has the permissions or role position needed in your server. Open Permission Health and Bot Logs in the authenticated dashboard to check server-specific failures. If the public status is unavailable across every shard, wait for the service to reconnect before changing Discord permissions.
When contacting support, include the affected server ID, the approximate time, the command or dashboard action attempted, and the resulting Bot Logs entry. Do not send bot tokens, authentication codes, passwords, or private ticket transcripts through a public channel.