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

    Friday 20th June 2025

    No incidents reported

    Thursday 19th June 2025

    No incidents reported

    Wednesday 18th June 2025

    No incidents reported

    Tuesday 17th June 2025

    Seattle Network Seattle inbound routing - NCP - higher latency for 20Gb/s IPs

    As of today, our inbound routing from the AS4134 NCP line (only used by our 20Gb/s DDoS protected IPs) has been disabled due to Ceranetworks closing their Portland POP. All inbound China routing now routes via Los Angeles therefore latency from China will have increased in many scenarios for 20Gb/s DDoS protected IPs. We are working on a feasibility study of whether we can obtain our own AS4134 NCP line, we currently do not have a time estimate.

    All non China inbound traffic for 20Gb/s DDoS protected IPs is temporarily being routed via Los Angeles too, this will be corrected in the coming days to route directly via Seattle instead.

    200Gb/s DDoS protected IPs are unaffected by this and have identical routing to before.

    Monday 16th June 2025

    No incidents reported

    Sunday 15th June 2025

    No incidents reported

    Saturday 14th June 2025

    Seattle Network China Mobile inbound routing change for 20Gb/s IPs

    The China Mobile (CMI) inbound routing for Seattle 20Gb/s DDoS protected IPs is currently offline as Ceranetworks' connectivity with them is temporarily disabled, potentially due to maintenance. Due to this, there will be higher latency for a small number of China Mobile regions due to routing going via Europe - something we have no control over without the CMI routing.

  • This has been resolved.

  • This will be resolved tomorrow (15th June).