Is Infraly down?

We are currently investigating this incident.

Our network provider has implemented a fix on their core network on 2026-05-18 18:37:23 UTC. Since then, our monitoring has shown positive traffic flow traversing the network. We will continue to monitor for the next 24 hours. If no issues, we will mark this as resolved.

Our monitoring is showing this is happening again. We have reached out to our network provider for an update. We will provide an update as soon as possible.

Type: Incident Duration: 9 days, 12 hours and 5 minutes Affected Components: Redcentric London City May 18, 17:36:52 GMT+0 - Investigating - We are currently experiencing an issue with our network provider in London. The provider has confirmed this is a core network issue, which accounts for the level of impact being observed. Their team is actively working to resolve the issue, and we will share further updates as soon as they become available. May 18, 19:22:29 GMT+0 - Monitoring - Our network provider has implemented a fix on their core network on 2026-05-18 18:37:23 UTC. Since then, our monitoring has shown positive traffic flow traversing the network. We will continue to monitor for the next 24 hours. If no issues, we will mark this as resolved. May 18, 21:24:57 GMT+0 - Resolved - Our monitoring is showing this is happening again. We have reached out to our network provider for an update. We will provide an update as soon as possible.

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.

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.

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.

Type: Incident Duration: 1 day, 14 hours and 30 minutes Affected Components: Game Hosting, Premium VPS, Dedicated Servers, Colocation, Budget VPS May 18, 07:11:42 GMT+0 - Monitoring - 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. May 18, 15:50:55 GMT+0 - Resolved - 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. May 17, 01:21:11 GMT+0 - Identified - 45.62.160.0/24 is experiencing routing issues. 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 the IP lease 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, such as us in this case, is permitted to route traffic to. We are working with the IP leaser to resolve this problem immediately. If you would like to change IP addresses to not encounter this issue, please open a ticket, and we will assist with doing so. We will provide updates as soon as possible.