All systems are operational

Past Incidents

Tuesday 25th June 2024

No incidents reported

Monday 24th June 2024

Seattle Network Seattle packet loss

Our Seattle network is seeing intermittent packet loss for our 20Gb/s DDoS protected IPs. We are aware of the cause and are working on resolving with our provider.

  • AS4837 has now been re-enabled.

  • We have temporarily re-routed away from AS4837 due to significant disruption to China bound traffic, we will reactivate as soon as our transport provider resolves the issue.

  • Intermittent packet loss of 10% on average, often 100% loss for up to 20 seconds, to China Telecom and Unicom. This is caused by the network transport provider we use for AS4837 having problems, we have sent them a message about it and are awaiting an update.

  • Sunday 23rd June 2024

    No incidents reported

    Saturday 22nd June 2024

    No incidents reported

    Friday 21st June 2024

    No incidents reported

    Thursday 20th June 2024

    No incidents reported

    Wednesday 19th June 2024

    Hong Kong Network HongKong network issues

    Our Hong Kong are faulty. We have contacted the upstream and are handling the problem.

  • The faulty device has been replaced and has been restored.

  • Estimated completion time: 20 minutes

  • Location: Hong Kong

    Date: June 22, 202

    Time: 11:00 AM HKT

    Duration: Estimated 15 minutes

    Reason: Over the past three days, there have been network interruptions in Hong Kong. Upon inspection, we found a hardware fault in the core router that could not be fully resolved, necessitating an immediate replacement.

  • It has been temporarily restored at present, and the new equipment we purchased has not yet been put in place.

  • The faulty equipment is being repaired. A bug occurs in the core equipment system. The interconnection LACP between the cores cannot establish contact.

  • The faulty device has been replaced and is now restored

  • Connectivity to China still seems to be problematic, we are working on it. You can monitor the status of the adjustments via https://ping.pe

  • The cause of the problem was a faulty router in the datacenter. We have purchased new equipment to replace it. It has been restored and we will continue to observe.