How to support IRCCloud on your network

If you operate an IRC server or network, please allow an increased session limit for connections from the following IP ranges

Connection pool hostname IPv4
IPv6 Networks

Reverse DNS

All our IPs have a correct forward and reverse DNS under the domain. You may wish to simply permit more connections based on reverse DNS lookups.

Identifying users

Each user can be uniquely identified for the purpose of bans, etc. by their ident-verified username, in the form [u|s]id[UID] (eg: uid123 for a free user or sid456 for a paid subscriber). Users are unable to change their user IDs.

IPv6 support

If your network supports IPv6 connections, we'll detect any AAAA records exposed in DNS, and favour those by default. This will allow us to assign each user a unique IPv6 address, mapped from their user ID, e.g. 2604:8300:100:200b:6667:1::[UID_IN_HEX]

This is the preferred way to allow IRCCloud support, since each IRCCloud user connects from their own unique address within our /64 range.

In case of v6 failure, make sure there are sensible session limits of the v4 IPs too, as IRCCloud will retry connections using IPv4 if IPv6 fails.

On IPv6, each IRCCloud user connects from their own IPv6 address, with forward and reverse DNS entries that look like id-[UID].[POOL_HOST], eg:

Some IRC servers will group a whole IPv6 subnet together for the purposes of session limits (for example, UnrealIRCD by default will consider our whole /64 as one host). If this is the case you will need to configure your server to allow a separate clone limit for each address in our IPv6 subnet.

Special arrangements

If any of these arrangements aren't possible on your network, please send a message to james on, or contact us at and we can discuss other options. Thanks!