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

    Monday 10th February 2025

    Seattle Network Seattle IGW1.10.2 + SEABKVM25 outage

    Seattle IGW1.10.2 dedicated servers and E5 KVM server SEABKVM25 are currently offline due to switch failure, this should come back online within around 15 minutes. We already have a scheduled maintenance later today to remove this failing switch.

  • Now back online, we'll be proceeding with the switch replacement later today to stop this happening again.

  • Sunday 9th February 2025

    No incidents reported

    Saturday 8th February 2025

    No incidents reported

    Friday 7th February 2025

    No incidents reported

    Thursday 6th February 2025

    No incidents reported

    Wednesday 5th February 2025

    No incidents reported

    Tuesday 4th February 2025

    Seattle 200Gb/s packet loss

    Seattle 200Gb/s DDoS protected IPs are currently seeing up to 15% packet loss and low inbound bandwidth throughput. We've notified Ceranetworks of the issue and are awaiting a resolution.

  • The packet loss stopped at 17:30 UTC and returned to normal shortly after. The cause was fiber cuts causing congestion on a transport network used for the 200Gb/s IPs.