Hyonix - Status Page

All systems operational

Cloudflare DNS not reachable
  • Monitoring
    Monitoring

    Our team is aware of an issue that affect connectivity to Cloudflare from our main upstream (Global Secure Layer).

    The root cause is that BHARTI Airtel (Cloudflare's upstream) mistakenly leaked Cloudflare prefixes in Los Angeles (while it should have stayed in India), causing network disruption for all networks that have PNI (Private network interconnection) with them. One of our upstream has PNI with them were impacted (due to having global backbone - all sites are interconnected and use Airtel's invalid route to Cloudflare instead).

    Most of the servers deployed on our platform using Cloudflare DNS as default, which is why the DNS error occurred. This issue is limited to Cloudflare only, all other networks were not impacted.

    The incident has lasted for 8 minutes and seems to be recovered at this time as Airtel has quickly fixed the leakage.

    This is not limited to us but is a widespread issue with other providers as well: https://downdetector.com/status/cloudflare/

    If you still experiencing the issue, please let us know via ticket!

    Thank you for your understanding.

Services
Operational

Hyonix Panel - Operational

Hyonix Backend - Operational

Hyonix API - Operational

Virtualization Hosts
Operational

California, USA (LAX1) - Operational

Texas, USA (DAL1) - Operational

Virginia, USA (IAD1) - Operational

Virginia, USA (IAD2) - Operational

New York, USA (NYC1) - Operational

Miami, Florida (MIA1) - Operational

London, UK (LON1) - Operational

Amsterdam, NL (AMS1) - Operational

Hong Kong, HK (HKG1) - Operational

Tokyo, JP (TYO1) - Operational

Sydney, AU (SYD1) - Operational

Core Networks
Operational

California, USA (LAX1) - Operational

Texas, USA (DAL1) - Operational

Virginia, USA (IAD1) - Operational

Virginia, USA (IAD2) - Operational

New York, USA (NYC1) - Operational

Miami, Florida (MIA1) - Operational

London, UK (LON1) - Operational

Amsterdam, NL (AMS1) - Operational

Hong Kong, HK (HKG1) - Operational

Tokyo, JP (TYO1) - Operational

Sydney, AU (SYD1) - Operational

Recent notices

July 13, 2024

July 12, 2024

July 11, 2024

July 10, 2024

Cloudflare DNS not reachable
  • Monitoring
    Monitoring

    Our team is aware of an issue that affect connectivity to Cloudflare from our main upstream (Global Secure Layer).

    The root cause is that BHARTI Airtel (Cloudflare's upstream) mistakenly leaked Cloudflare prefixes in Los Angeles (while it should have stayed in India), causing network disruption for all networks that have PNI (Private network interconnection) with them. One of our upstream has PNI with them were impacted (due to having global backbone - all sites are interconnected and use Airtel's invalid route to Cloudflare instead).

    Most of the servers deployed on our platform using Cloudflare DNS as default, which is why the DNS error occurred. This issue is limited to Cloudflare only, all other networks were not impacted.

    The incident has lasted for 8 minutes and seems to be recovered at this time as Airtel has quickly fixed the leakage.

    This is not limited to us but is a widespread issue with other providers as well: https://downdetector.com/status/cloudflare/

    If you still experiencing the issue, please let us know via ticket!

    Thank you for your understanding.

July 09, 2024

July 08, 2024

July 07, 2024

Show notice history