Some systems are experiencing issues

Stickied Incidents

Saturday 18th October 2025

Seattle Network Seattle - China network performance (AS4837)

Our standard China optimised networking (AS4837) in Seattle is currently seeing high latency, packet loss and low bandwidth throughput, this is likely caused by a fiber cut in China Unicom's network, we do not have a estimated date for repair currently, in the past, such issues have usually been resolved within days.

Our premium China route (9929-CMIN2) is not impacted by this issue.

Monday 13th October 2025

Dallas network issues

Our Dallas DDoS protected network is currently seeing issues due to an issue on CosmicGuard's side, the issue only impacts IPs that have filters enabled, we anticipate it'll be fixed within the next few minutes.

  • The issues were resolved at 20:14 UTC.

  • Thursday 2nd October 2025

    Seattle Network Seattle network instability

    Our DDoS protected Seattle network is seeing ongoing intermittent disruption due to issues with our DDoS mitigation provider, Neoprotect. There is ongoing disruption with most DDoS mitigation providers currently and they are unfortunately affected too - they're working on solutions to the causes to get things stable again as soon as possible. This only impacts non China routes.

  • Neoprotect's network has been stable for many days now so we consider this resolved.

  • Past Incidents

    Monday 29th January 2024

    No incidents reported

    Sunday 28th January 2024

    No incidents reported

    Saturday 27th January 2024

    No incidents reported

    Friday 26th January 2024

    No incidents reported

    Thursday 25th January 2024

    No incidents reported

    Wednesday 24th January 2024

    No incidents reported

    Tuesday 23rd January 2024

    SEABKVM22 SEABKVM22 - Offline

    We have noticed an issue with SEABKVM22 that has caused it to lockup. We are currently rebooting the server and investigating what has caused it.

  • Started to come back online at 23:34 UTC. The system kernel panicked and a reboot brought it back up, we've updated the kernel in case this has a positive impact if the same issue reoccurs.