Hyonix - Notice history

All systems operational

Operational

Hyonix Panel - Operational

Hyonix Backend - Operational

Hyonix API - Operational

Operational

Los Angeles, California (LAX1) - Operational

Dallas, Texas (DAL1) - Operational

Ashburn, Virginia (IAD2) - Operational

New York, New York (NYC2) - Operational

Miami, Florida (MIA1) - Operational

London, United Kingdom (LON1) - Operational

Amsterdam, Netherlands (AMS2) - Operational

Hong Kong, Hong Kong (HKG1) - Operational

Tokyo, Japan (TYO1) - Operational

Sydney, Australia (SYD1) - Operational

Frankfurt, Germany (FRA10) - Operational

Toronto, Canada (TOR10) - Operational

Chicago, Illinois (CHI1) - Operational

Operational

Los Angeles, California (LAX1) - Operational

Dallas, Texas (DAL1) - Operational

Ashburn, Virginia (IAD2) - Operational

New York, New York (NYC1) - Operational

New York, New York (NYC2) - Operational

Miami, Florida (MIA1) - Operational

London, United Kingdom (LON1) - Operational

London, United Kingdom (LON-THN) - Operational

Slough, United Kingdom (LON5) - Operational

Amsterdam, Netherlands (AMS2) - Operational

Amsterdam, Netherlands (AMS-NIKHEF) - Operational

Hong Kong, Hong Kong (HKG1) - Operational

Tokyo, Japan (TYO1) - Operational

Sydney, Australia (SYD1) - Operational

Frankfurt, Germany (FRA10) - Operational

Toronto, Canada (TOR10) - Operational

Chicago, Illinois (CHI1) - Operational

Notice history

Sep 2025

Console Feature Not Available
  • Resolved
    Resolved

    Our team has been able to confirm that Console feature is fully restored at this time.

    If you still face any issues with our Console feature, please try to clear current browser cache and try again! If the issue still exists after the cache clear, please open a ticket and our team will look into the issue as soon as possible.

    This issue has now been resolved.

  • Identified
    Identified
    Our team is aware of an issue that affect Console features in the following locations: Los Angeles, Dallas, London, Amsterdam, Frankfurt, Singapore, Hong Kong, Japan. The issue is caused due to underlying upstream network outages, our team is monitoring the issue and will provide update as soon as we heard back. Please note that while Console Feature is unavailable at this time, all servers are not affected and are fully operational. If you were using Console as main remote method to the server, please use Remote Desktop Protocol (RDP) to connect to your server instead. Our apologies for any inconvenience caused. We are actively working with upstream to resolve this issue.

Aug 2025

Amsterdam, Netherlands (AMS1) Network Partial Outage
  • Resolved
    Resolved

    All services have been brought back online. This issue was caused by a network configuration conflict during routine maintenance.

    The issue lasted for 18 minutes and has been fully restored at this time.

    We sincerely apologize for any inconvenience caused.

    If you have any questions, please let us know by opening a ticket!

  • Identified
    Identified

    Our team is aware of an issue that causing Amsterdam to lose connectivity, our team is working to get it back online.

    Further updates will be provided once we receive new information from Network Operation Center (NOC).

Frankfurt, Germany (FRA10) Partial Network Outage
  • Resolved
    Resolved

    As there is no further issues, our team will now close this incident.

    If you have any issues, please let us know by opening a ticket!

  • Monitoring
    Monitoring

    Our upstream has confirmed that the issue originated from their end due to a fiber maintenance, causing partial outages to our network (some IPs becomes unreachable, some still reachable) as it still being routed through the taken-down fiber.

    They have now properly shutdown the stale route and all services are back online.

    We will put this incident on monitoring state and will be closely watching to ensure this does not happen again.

    If you still have any issues, please let us know by opening a ticket!

  • Investigating
    Investigating

    Our team has been aware of a network issue that causing servers to become unreachable. We are currently investigating this incident.

    Our technical team has already performed troubleshooting process and confirmed that all configurations on our ends are properly set up. We are engaging our upstream in this location for further clarification.

    Technician is being dispatched on-site to check if there is any issues with our networking hardwares.

    Currently we are observing approximately 8% of servers experiencing issues in this region. The trends seems to be increasing by the hour, our team is actively working to get this resolved as soon as possible. It is also confirmed that the issue is network-related and not power-related.

    We sincerely apologize for any inconvenience caused, our team will post updates as new information becomes available to us.

    Thank you for your patience and understanding!

Jul 2025

Los Angeles, California (LAX1) Network Instability
  • Resolved
    Resolved

    This incident has been marked as resolved as we do not see any further issues at this time.

  • Monitoring
    Monitoring

    Upstream routers that we connected to was having loads issue, resulting in heavy packet losses and intermittent connectivity. Our team observed that in some case the connectivity was lost for up to 11 minutes.

    Currently the issue has been fixed and our main upstream has been re-activated. Our team will continue to monitor this issue closely and will update if we detect any problems.

    We sincerely apologizes for any inconvenience caused - Please do let us know if you have any further questions by opening a ticket.

  • Identified
    Identified

    We've fallen back to our backup to ensure reachability, networks currently remains stable, however some routes might not be optimal at this time until our main link becomes available. We will provide updates once we hear back from upstream NOC.

  • Investigating
    Investigating

    Our team is aware of an issue that impact our network reachability. We are looking into this and will provide updates as more information available to us.

    We are observing very high packet losses toward from our upstreams. Currently reaching out to them for resolution. Our engineer will start falling back to our backup link if not resolved within a few minutes.

Ticket Responses Not Being Imported Through Email
  • Resolved
    Resolved

    All tickets have been processed and followed up at this time. We will proceed to close this incident as it has now been wrapped up!

    Our team has also implemented checks in place to ensure this will not happen again in the future.

    Thank you for your patience and understanding on this issue.

  • Update
    Update

    We've processed over 60% of past tickets at this time, our team is still working actively to get the remaining tickets processed.

    If you have any unanswered questions or unresolved issues, please let us know by opening a new ticket or replying to the existing ticket so our team can prioritizes accordingly.

    Thank you for your patience and understanding.

  • Identified
    Identified

    Our team has identified an issue that caused ticket responses via emails not being imported properly. The root cause is due to Google disabling password authentication method: https://workspaceupdates.googleblog.com/2023/09/winding-down-google-sync-and-less-secure-apps-support.html

    Our team has checked and confirm that we have not received any notification about this change on our account with Google Workspace. This is why we have been unaware of this change and did not switch authentication method accordingly. We only came to aware of this issue due to recent reports from clients. Our backend platform (WHMCS) also did not handle the error or report this error to our logs so we were unable to detect it.

    At this time, we have begun to process old ticket replies and will notify affected customers of this issue, and follow up with customers questions that have not been answered. All ticket response through our platform was not impacted.

    It is estimated that the current queue to be fully processed within 2 days. Our team will post updates as we progresses.

    We sincerely apologizes for any inconvenience caused by this issue. Our development team has started to look into how to catch this error so we don't have the same issue in the future.

Jul 2025 to Sep 2025

Next