3 ms·
This issue should be resolved. It is early but appears our DDoS systems kicked in when they shouldn't.
by dknecht 8y ago
This issue should be resolved. It is early but appears our DDoS systems kicked in when they shouldn't.
- sslalready 8y agoThanks for the update. Did this affect all of your public resolvers or only 1.1.1.1?
- ngnear 8y agoIt only affected 1.1.1.1 and 1.0.0.1 over UDP. The IPv6 pairs 2606:4700:4700::1111 and 2606:4700:4700::1001 were unaffected.
- ben174 8y agoYou might want to put a link to your system status page on your home page: https://1.1.1.1/ https://1.1.1.1/ I googled "1.1.1.1 service status" and that was the top result and there was no link to your actual status page. So then I did what I always do and hit https://news.ycombinator.com/newest https://news.ycombinator.com/newest
- ngnear 8y agohttps://www.cloudflarestatus.com/incidents/2mz3wly2g7dy https://www.cloudflarestatus.com/incidents/2mz3wly2g7dy Sorry about that. https://www.cloudflarestatus.com/ https://www.cloudflarestatus.com/ should also encompass 1.1.1.1 and 1.0.0.1.