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

Aug 2023

Hyonix Panel Update
  • Completed
    August 28, 2023 at 10:32 AM
    Completed
    August 28, 2023 at 10:32 AM

    Our team has successfully updated our panel and backend!

    Users can now access Hyonix Panel normally.

    If you face any unexpected issues or have any feedbacks, please le tus know via ticket!

  • In progress
    August 28, 2023 at 9:20 AM
    In progress
    August 28, 2023 at 9:20 AM

    Maintenance is now in progress

  • Planned
    August 28, 2023 at 9:20 AM
    Planned
    August 28, 2023 at 9:20 AM

    Our team is currently updating Hyonix Panel and Backend. We expects the update to be completed within 2 hours.

    If you have any emergency query, please email us at hello@hyonix.com

    Thank you for your patience and understanding.

Brief Network Disruption in IAD1/2, LAX1, NYC1, AMS1
  • Resolved
    Resolved

    We have received a notification from our upstream provider, GSL Network, regarding a temporary interruption in the network. This disruption primarily affected outbound traffic and lasted for approximately 6 minutes around 9:00AM UTC.

    During this timeframe, your server is still reachable but might not be able to connect to other services.

    The network was then re-routed and everything has been back up and running.

    Our upstream notification for reference: https://www.gslstatus.com/incidents/6rv7rz3mfqc5

    If you are still seeing issues, please open a ticket so we can check it out for you!

    Our apologies for any inconvenience caused - Thank you for understanding!

Network interruption in Virginia (IAD2)
  • Resolved
    Resolved

    We've discovered that this was caused by a small BGP error, the error has now now been removed/fixed.

  • Investigating
    Investigating

    Around 2:05AM, there was a small outage on our second core in IAD2 for 1 minute. The issue is currently unknown. We will continue to update as we learn more of the situation. IAD2 network is still online using our redundant link to GSL.

Jul 2023

Network interruption in Virginia (IAD2)
  • Resolved
    Resolved

    As there was no further issues after 5 days, we will now close this incident!

    If you have any further questions, please let us know.

  • Update
    Update

    GSL Network has confirmed that the maintenance is completed, the network loads have been restored to their transit on our IAD2 network.

    We aplogizes for any inconvenience caused.

    This status will remain active as we monitor the situation in the next 24 hours.

  • Monitoring
    Monitoring

    Our IAD2 network has now been restored, however our main uplink to GSL network is still under maintenance. We will monitor the progress and bring GSL network back up on our blend after they've completed maintenance.

  • Update
    Update

    Our technician has arrived on-site and currently working on a fix as we updates.

  • Identified
    Identified

    It appears that uplinks from our Upsteam has been cut off due to an emergency maintenance on their side: https://www.gslstatus.com/incidents/sl5s1fr8qgvx

    We did have redundancy in place, however it was not kicked in due to a stale configuration from the previous maintenance in IAD1 (where our team has upgraded our core switches).

    We are currently waiting for on-site tech to be arrived to do further troubleshooting and bring network back up.

  • Investigating
    Investigating

    Our team has been aware that our IAD2 network has become unreachable. We are currently looking into it.

Jun 2023

Network interruption in Virginia (IAD2)
  • Resolved
    Resolved

    This incident has been resolved as our team did not see any issues with the affected components!

  • Monitoring
    Monitoring

    Our technician is currently on-site and has replaced the network optics, our NOC has confirmed that all uplinks are now back operational!

    We are still actively monitoring this issue in the next 24 hours to see if there is any further problems.

    If you are still seeing issues, please reach out to us via ticket!

    Thank you for your patience and understanding.

  • Identified
    Identified

    It appears that one of our core uplinks was flapping due to a hardware (optics) issue, causing high packet loss/error rate. Our NOC has now disabled the faulty uplink and all traffic has been rerouted to our second uplink.

    Our on-site tech is currently en-route for hardware replacement.

    All servers have been back operational at this time.

    We apologize for any inconvenience caused.

    Thank you for your patience and understanding!

  • Investigating
    Investigating

    Our team is aware that our IAD2 location is currently unreachable. Our NOC is currently looking into this.

    We will post updates as we receive more information.

    Thank you for your patience and understanding.

Network interruption in Virginia (IAD1)
  • Resolved
    Resolved

    There was a conflicted configuration on one of our edge switch that caused the uplink flaps, this has now been resolved!

    The incident only affected a small portion of host nodes starting with IAD1 prefix, IAD2 host nodes are not affected.

    If you still having issues, please hit up a ticket!

    Thank you for your patience and understanding on this matter.

  • Identified
    Identified

    Our team is aware of network interruptions with a few host nodes in IAD1 locations.

    Our NOC is currently working on this and will provide updates as we have more information!

    Thank you for your patience and understanding!

Jun 2023 to Aug 2023

Next