Infraly - Chicago - 45.62.160.0/24 Routing Issues
Timeline · 3 updates
- identified May 17, 2026, 01:21 AM UTC
This prefix is one of our last remaining leased prefixes as we have moved solely to deploying new systems on fully-owned prefixes. From our initial investigation, this routing issue is caused by a bug in our IP leasers systems where their automation removed the ROA and RPKI objects for the IP subnet. These two objects are how internet providers know that a provider, us in this case, is permitted to route traffic to. We are working with the IP leaser to resolve this problem immediately. We will provide updates as soon as possible.
- monitoring May 18, 2026, 07:11 AM UTC
The IP holder has confirmed this was an issue on their end and has re-created the ROA and RPKI objects for 45.62.160.0/24\. As these changes propagate, routing to the prefix will be restored. Most networks should see connectivity return within the next few hours, though some providers may take longer to refresh their RPKI validators.
- resolved May 18, 2026, 03:50 PM UTC
Connectivity to 45.62.160.0/24 has been fully restored across all networks. Due to this incident, we will be phasing out this prefix over the next 1-2 months and migrating affected systems to new prefixes. If your service is affected, you will receive an email with your new IP address(es) and migration details ahead of the change. We apologize for the disruption and appreciate your patience.