Infraly had 7 outages in the last 2 years totaling 1220h 39m of downtime — averaging 0.3 incidents per month.
There were 7 Infraly outages since October 29, 2025 totaling 1220h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
Since 15:55 UTC, our monitoring has reported WISP front-end services have been periodically inaccessible. Our team is currently looking into the issue. We will provide an update as soon as possible..
This has been resolved..
We are currently investigating this incident.
Traffic is traversing the network normally again. We observed a flap on one of our carrier ports that caused a period of packet loss and reachability issues for some customers. We are continuing to monitor the affected port and are working with our transit provider to determine the root cause. We will update this incident once we have more information.
After further investigation with our transit provider, we traced the instability to a control plane issue on one of our edge routers, which was negatively affecting traffic traversing the associated carrier port. The port itself and our provider's network were not at fault. We have applied adjustments to the affected router to correct the behavior. Traffic has been traversing the network normally since 19:13 UTC, with no recurrence since the changes were made. We will continue to keep additional monitoring on this router. We apologize for the disruption and appreciate your patience. If you are still experiencing issues with your services, please open a ticket with our support team.
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.
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.