All systems are operational

Stickied Incidents

Saturday 28th June 2025

Seattle Network Increased latency for China

We're currently seeing increased latency to/from China for our Seattle network due to suspected fiber cuts on the US west coast, this appears to be heavily impacting China Unicom's network (AS4837) which has likely lost considerable capacity. CMIN2 should not see any impact apart from a temporary 20ms latency increase due to a re-route caused by the fiber cuts. This shouldn't take too long to be resolved.

  • The fiber cut was fixed at 4pm UTC and we can confirm everything is now looking normal.

  • Confirmed fiber cut, here is the explanation from our transport provider: There is a fiber cut between Vacaville, CA and Sacramento, CA. The fiber cut was caused by a car hitting a utility pole.

    It's likely that China Unicom is suffering capacity loss due to this same incident, there is no estimated fix time yet.

  • Past Incidents

    Thursday 14th April 2022

    SEAHKVM2 SEAHKVM2 offline

    Seattle VPS server SEAHKVM2 is currently offline, we're investigating.

  • SEAHKVM2 is now back online, we apologise for the inconvenience caused.

  • Wednesday 13th April 2022

    No incidents reported

    Tuesday 12th April 2022

    No incidents reported

    Monday 11th April 2022

    No incidents reported

    Sunday 10th April 2022

    No incidents reported

    Saturday 9th April 2022

    SEAKVM11 offline

    SEAKVM11 is currently offline, we're investigating.

  • Server is now back up, no reboot was needed, apologies for the inconvenience.

  • This is still being worked on, the cause appeared simple to begin with but it has turned out more complicated than we hoped.

  • The cause appears to be related to the network uplink for this server, we're waiting on data centre staff checking it.

  • Friday 8th April 2022

    No incidents reported

    Thursday 7th April 2022

    SEABKVM4 SEABKVM4 offline

    SEABKVM4 is currently offline, we're investigating.

  • Server is now back online after the RAM replacement.

  • RAM replacement is now occurring, ETA is maximum 30 minutes.

  • The fault causing the downtime is RAM related, we're working on a replacement.