We were using 44.24.221.1 as the gateway address.
[...]
We'd have to reconfigure things a bit and utilize another IP address from our ISP to get it running on a non-44 gateway IP.
HamWAN had to switch to using a 44 ip on the IPIP endpoint when it became an independent autonomous system on the internet. In order to maintain shortest path and high availability, the IP needs to be on one of the prefixes that HamWAN announces directly (which is only 44-based prefixes). If another ISP's address was used instead, the traffic would be forced to travel though (and have a dependency on) that specific ISP's network.
The ideal workaround would be to get a /24 outside of 44/8 that HamWAN could announce from its ASN. That's not only prohibitively expensive, but a waste of resources and a silly thing to do just to route around the misconfigurations of others.
As a result, it was decided that it was better to maintain high availability for those who wanted to actively use the HamWAN network instead of making it less available, but generally reachable to all 44net users.