Some systems are experiencing issues

Stickied Incidents

Sunday 12th April 2026

Seattle Network Elevated latency in Seattle

We're currently seeing significantly elevated latency for our Seattle DDoS protected network, of around 66ms. This is caused by multiple fiber cuts in the transport network we use to San Jose. We've been given an ETA for one of the cuts to be resolved on 13th April by 13:00 UTC, but we're hopeful the separate fiber cut that occurred at 10:36 UTC today (12th April) will be resolved long before this.

  • One of the fiber cuts in our transport provider's network was resolved at 03:10 UTC today (13th April) however there was a period of intermittent instability after this, ending at 03:54 UTC, likely related to the restoration of the route.

  • Thursday 30th October 2025

    Seattle Network Seattle network latency

    Our Seattle DDoS protected network saw instability starting at 20:37 UTC and ending at 20:45 UTC, this was caused by one of our DDoS mitigation providers, Neoprotect, suffering a full network outage, our backup network automatically took over within minutes and this will remain active until Neoprotect is stable again.

    See the update below for full details:

  • Neoprotect has stated that they are not going to continue their service. We are investigating alternative DDoS mitigation providers and hope to have one available soon, this will also return latency to normal levels.

  • Neoprotect is still offline, they use datapacket/CDN77 as a sole upstream and they disabled Neoprotect's service which resulted in the full global outage of Neoprotect's network. You can read more about the cause here: https://status.neoprotect.net

    We are currently routing DDoS protected inbound traffic through Cnservers Los Angeles so there will be a latency increase for locations that are geographically close to Seattle, if this is a problem for you in the short term, please contact us and we'll discuss the options available with you.

    Longer term, we will onboard another ddos mitigation provider, potentially GSL, that has a local Seattle POP, this will ensure latency is normal.

  • Past Incidents

    Tuesday 14th April 2026

    No incidents reported

    Monday 13th April 2026

    No incidents reported

    Sunday 12th April 2026

    Seattle Network Elevated latency in Seattle

    We're currently seeing significantly elevated latency for our Seattle DDoS protected network, of around 66ms. This is caused by multiple fiber cuts in the transport network we use to San Jose. We've been given an ETA for one of the cuts to be resolved on 13th April by 13:00 UTC, but we're hopeful the separate fiber cut that occurred at 10:36 UTC today (12th April) will be resolved long before this.

  • One of the fiber cuts in our transport provider's network was resolved at 03:10 UTC today (13th April) however there was a period of intermittent instability after this, ending at 03:54 UTC, likely related to the restoration of the route.

  • Saturday 11th April 2026

    No incidents reported

    Friday 10th April 2026

    No incidents reported

    Thursday 9th April 2026

    No incidents reported

    Wednesday 8th April 2026

    No incidents reported

    Tuesday 7th April 2026

    Seattle Network Seattle AS9929 routing issue

    Our Seattle AS9929 China optimised routes are currently re-routed due to high packet loss and latency seen since 07:20 UTC. We've re-routed China Telecom via AS4837 and Unicom via CMIN2.

    There's likely a fiber cut or equipment failure in Los Angeles causing this, we're monitoring and will re-enable AS9929 as soon as the issue is resolved. We have not been given an estimated fix time yet, we'll update this entry if we get any updates.

  • AS9929 has been reactivated since 09:17 UTC as it became stable.