All systems are operational

Stickied Incidents

Friday 26th April 2024

Seattle Network Reduced China network performance

Our network transport provider that we use to reach AS4837 from Seattle has gone offline. We have temporarily switched the outbound route to China to use AS4134.

  • This has now been resolved and AS4837 outbound routing to China Telecom and Unicom is now active again.

  • We have been informed the cause is a fiber cut along the route, our transport provider said they cannot provide an ETA currently.

  • Past Incidents

    Saturday 16th April 2022

    DALSKVM3 offline

    Dallas storage KVM, DALSKVM3, is currently offline due to raid array issues, we're investigating.

  • Server came back online at 08:16 BST and all VPS's are now fully booted up.

  • We found the raid card performing a consistency check however it says it is in an optimal state. Upon rebooting the server, the operating system started fsck'ing the file system which it is doing now, no ETA.

  • Friday 15th April 2022

    DALSKVM2 read-only file system

    Dallas KVM storage VPS server, DALSKVM2, is currently in a read-only file system due to problems caused by a drive swap in the raid array to replace a faulty disk, we're checking what happened.

  • VPS's started coming back online 14 minutes ago and are now all back online, we anticipate that this issue is now resolved.

  • 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 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.