We're currently seeing network disruption in Seattle, China Unicom is currently suffering the most issues. It appears there has likely been major fiber cuts, we're investigating.
Transport provider's route has gone back to a long distance re-route so latency will have increased again, hopefully won't take too long to reduce back to normal again.
Our transport provider has confirmed they suffered multiple fiber cuts in a very short time period which is what caused the outages and high latency. A path has since come back online so latency has reduced to only 17ms above normal, this will be resolved later today as soon as the fiber cut can be repaired. China Unicom routing via AS4134 has been restored.
China Unicom connectivity has been restored, AS4134 stopped routing traffic to AS4837 - likely related to the major suspected fiber cut event on US west coast. We're still checking the quality of the network overall. Latency will be temporarily relevated due to the fiber cuts.
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.
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.
Our DDoS protected Dallas network is currently offline due to an issue on CosmicGuard's side, we are talking to them.
It has since become known that Cloudflare is currently performing large-scale maintenance in many of their locations, their Dallas location went completely offline for the period we were offline, so this explains why we saw an outage. There was likely something that went wrong on Cloudflare's side in another of their locations that somehow then impacted Dallas, CosmicGuard is setup to automatically fail us over to another of their locations in the event of BGP routes being pulled - something that Cloudflare did not do in Dallas for an unknown reason. CosmicGuard will be talking to Cloudflare about this in the hope of avoiding a repeat.
Dallas came back online at 08:40 UTC. CosmicGuard has been using Cloudflare Magic Transit recently to help absorb the large attacks that DDoS mitigation providers are being hit with nowadays, 20Tb/s+. Unfortunately Cloudflare suffered a connectivity issue to CosmicGuard in Dallas, which resulted in traffic being blackholed, essentially dropped. CosmicGuard is currently investigating with Cloudflare why this happened, to hopefully prevent a repeat. We apologise for the inconvenience caused.
No incidents reported
No incidents reported
No incidents reported
No incidents reported
No incidents reported