TUES May 28 7:39AM We are currently experiencing a network interruption. Our engineering team is investigating and we will provide an update within 30 minutes.
UPDATE TUES May 28, 8:17AM Sail Internet is currently experiencing a targeted DDoS attack. Our engineering team is working hard to analyze, mitigate, and resolve. [This type of attack is designed to overwhelm a system, and there is no danger to customers other than slow or no service.]
UPDATE 9:17AM - We have identified the source of the attack and the affected devices. The main issue is that our network is flooded with traffic so it's even hard for us to get around. Imagine having to wade upstream against a raging torrent to get to an upstream target. That's what our engineers have to do...
UPDATE 9:30AM We are making good progress towards resolving this issue. We have isolated the devices/interfaces under attack. We are working to resolve this issue as soon as possible.
UPDATE 9:50AM Engineers have isolated the specific target devices and are working to filter out bad traffic.
UPDATE 10:15AM Engineers have filtered out a big chunk of the bad traffic on our internal network. We have regained control of our network so now at least we can get around. Now working on fixing what needs to be fixed.
UPDATE 10:35AM Some devices are still under attack. Also, this seems to be a multi-layered attack. The attacks are shifting as we find them. We are working to analyze and isolate these.
UPDATE 11:04AM We are making progress on isolating devices. We still have no ETA on when service will be restored. Next update will be when we have more information. Thank you.
UPDATE 1:25PM As engineers add filtering and selective blocking, things are gradually recovering as the filtering goes into effect. Some service may be available at degraded speeds, and not all destinations may be available.
UPDATE 1:43PM Service has been mostly restored. More details to follow...
UPDATE 1:50PM The DDoS attack has been mitigated, and our network is operating normally.
Comments
0 comments
Article is closed for comments.