Infraly Outage History

Infraly major outage · 1 active incident View live status →

Infraly had 8 outages in the last 2 years totaling 1219h 56m of downtime — averaging 0.3 incidents per month.

There were 8 Infraly outages since October 29, 2025 totaling 1219h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.infraly.co

Minor September 2, 2026

Infraly - Chicago - Network Connectivity Issues

Detected by Pingoru
Sep 02, 2026, 06:52 PM UTC
Resolved
Sep 02, 2026, 08:11 PM UTC
Duration
1h 19m
Affected: Chicago, Illinois (Equinix CH1)Chicago, Illinois (SBA Edge)Chicago, Illinois (Backbone Network)
Timeline · 3 updates
  1. investigating Sep 02, 2026, 06:52 PM UTC

    We are currently investigating this incident.

  2. investigating Sep 02, 2026, 07:03 PM UTC

    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.

  3. resolved Sep 02, 2026, 08:11 PM UTC

    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.

Read the full incident report →

Minor May 18, 2026

Infraly - London - Network

Detected by Pingoru
May 18, 2026, 05:36 PM UTC
Resolved
Jul 06, 2026, 09:44 PM UTC
Duration
49d 4h
Affected: London, United Kingdom (Telehouse North)London, United Kingdom (Redcentric London City)London, United Kingdom (Backbone Network)
Timeline · 3 updates
  1. investigating May 18, 2026, 05:36 PM UTC

    We are currently investigating this incident.

  2. monitoring May 18, 2026, 07:22 PM UTC

    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.

  3. monitoring May 18, 2026, 09:24 PM UTC

    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.

Read the full incident report →

Minor May 17, 2026

Infraly - Chicago - 45.62.160.0/24 Routing Issues

Detected by Pingoru
May 17, 2026, 01:21 AM UTC
Resolved
May 18, 2026, 03:50 PM UTC
Duration
1d 14h
Affected: Physgun (Game Hosting)Physgun (Dedicated Servers)Physgun (Colocation)Physgun (Premium VPS)Physgun (Budget VPS)
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Major October 29, 2025

WISP - Front-end Outage

Detected by Pingoru
Oct 29, 2025, 01:10 PM UTC
Resolved
Oct 29, 2025, 01:10 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 29, 2025, 01:10 PM UTC

    Type: Incident Duration: 15 hours and 14 minutes Affected Components: Panel, Billing Oct 29, 13:10:00 GMT+0 - Investigating - At 13:10 UTC, our monitoring reported WISP front-end services became inaccessible due to an issue with Cloudflare. Our team is currently working on recovering and bringing online. Oct 29, 13:37:00 GMT+0 - Resolved - At 13:37 UTC, front-end services have returned back online. We're in touch with our account manager and support staff at Cloudflare. If any users are experiencing issues, please follow the proper support channels.

Read the full incident report →