Our Dallas DDoS protection provider, CosmicGuard, is suffering global network issues due to very large ddos attacks coming from a known 40Tb/s botnet, they're working on resolving the situation as soon as possible, no exact ETA currently available.
Stability returned at 12:01 UTC, CosmicGuard has posted a RFO here: https://status.as30456.net/cmiivbxm6004wt518aafiq5dd
We're seeing ongoing long outages, we're still awaiting an update from CosmicGuard.
CosmicGuard saw a brief global outage from 09:49 - 09:53 UTC, issues with specific POPs are ongoing.
CosmicGuard started global maintenance at 17:58 UTC and it appears it caused a global outage rather than only in Los Angeles, things have since came back starting at 18:04 UTC.
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.
No incidents reported
No incidents reported
SEAKVM11 is currently offline, we're investigating.
This has been resolved.
This issue is requiring further advanced diagnostics as reorganising how the SSDs are connected to the motherboard did not improve the situation.
We've identified that the issue relates to the server's PCIe card that connects the SSDs to the server. We're working on reconfiguring the hardware to remove this issue.
No incidents reported
No incidents reported
No incidents reported
No incidents reported