What are the ChannelEngine IP-ranges?

// IP-ranges

ChannelEngine uses the following IP's / IP-ranges:

Range From To
2a01:07c8:2928:0000:0000:0000:0000:0000 2a01:07c8:2928:ffff:ffff:ffff:ffff:ffff
2001:982:13f7::/48 2001:982:13f7:0000:0000:0000:0000:0000 2001:982:13f7:ffff:ffff:ffff:ffff:ffff
2001:41f0:144f::/48 2001:41f0:144f:0000:0000:0000:0000:0000 2001:41f0:144f:ffff:ffff:ffff:ffff:ffff
2001:4cb8:fe26:30::/64 2001:4cb8:fe26:30:0000:0000:0000:0000
2001:4cb8:fe26:40::/64 2001:4cb8:fe26:40:0000:0000:0000:0000
2001:4cb8:fe26:50::/64 2001:4cb8:fe26:50:0000:0000:0000:0000 2001:4cb8:fe26:50:ffff:ffff:ffff:ffff

// I can't whitelist / allowlist ranges, don't you have a single IP?

This is a request we do receive once in a while. However, as we have multiple servers running tasks for ChannelEngine, each with different IP-ranges configured, and also have several office IP's we do not have 1 or just a few IP's that need to be whitelisted. While we are considering looking into the option of adding an (optional) outgoing proxy in order to facilitate this request, this would introduce both a delay (all data would have to be transmitted through one or more additional servers) and a single point of failure (if that single IP is blacklisted / denylisted, DDoS'ed or the proxy is down no tasks could be performed).

As most modern firewall software allows for the whitelisting (or allowlisting) of entire ranges and the previously mentioned downside of adding such a proxy, this is currently not on our short term roadmap.