Hyonix Outage History

Hyonix had 2 outages in the last 2 years totaling 2h 6m of downtime — averaging 0.1 incidents per month.

There were 2 Hyonix outages since July 22, 2026 totaling 2h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hyonix.com

Minor September 2, 2026

LAX1 Internet Connectivity Loss

Detected by Pingoru: Sep 02, 2026, 05:43 PM UTC
Resolved: Sep 02, 2026, 07:10 PM UTC
Duration: 1h 26m

Affected: Core Networks (Los Angeles, California (LAX1))

Timeline · 3 updates

investigating Sep 02, 2026, 05:43 PM UTC

We are aware of an network issue affecting our LAX1 location. We are currently investigating this incident.
monitoring Sep 02, 2026, 05:58 PM UTC

Our primary upstream network device hit a panic state and forced a reboot, all traffic has been rerouted to alternate path at this time. All servers remains operational and connectivity has been restored at this time. We observed the loss duration to be up to 18 minutes. Our team will continue monitoring the situation closely and will reroute back to primary path once confirmed to be stable.
resolved Sep 02, 2026, 07:10 PM UTC

Upstream has confirmed that device is running stable at this time, primary route has been reinstated. This incident is now marked as resolved.

Read the full incident report →

Minor July 22, 2026

Frankfurt, Germany (FRA10) Partial Outage

Detected by Pingoru: Jul 22, 2026, 02:51 PM UTC
Resolved: Jul 22, 2026, 03:31 PM UTC
Duration: 39m

Affected: Core Networks (Frankfurt, Germany (FRA10))

Timeline · 2 updates

monitoring Jul 22, 2026, 02:51 PM UTC

Our team is aware that there's a network issue impacting our FRA10 location. Currently network has been restored, we are reaching out to upstream for further clarification at this time and will provide updates once we receive new information. Customers with deployment in our FRA1 location is not impacted by this issue. Our apologies for any inconvenience caused.
resolved Jul 22, 2026, 03:31 PM UTC

Our upstream has confirmed that the issue was due to a filter update error on their end that dropped our subnets from their network. A fix was quickly implemented and all services were back online. If you have any further questions, please let us know by opening a ticket! Thank you for your patience and understanding on this matter.

Read the full incident report →