4 ms·
Looks like L3, Azure and Google are all being affected by a DNS DDoS attack.
by certifiedloud 6y ago
Looks like L3, Azure and Google are all being affected by a DNS DDoS attack.
- geitir 6y agohow can you tell?
- feyman_r 6y agoAWS: https://downdetector.com/status/aws-amazon-web-services/ https://downdetector.com/status/aws-amazon-web-services/ Cloudflare: https://downdetector.com/status/cloudflare/ https://downdetector.com/status/cloudflare/
- feyman_r 6y agoAnd Google too: https://downdetector.com/status/google/ https://downdetector.com/status/google/
- ceejayoz 6y agoDownDetector is worthless. There’s no reason to put any stock in it. Look at the comments on any entry and it’s clear people do stuff like report “outages” for Google because a random website won’t work in Chrome.
- lima 6y agoThe data is still useful in aggregate.
- ceejayoz 6y agoMarginally, if anything. Non-technical users misattribute and misunderstand causes of outages. There’s a comment on the AWS page complaining that iTunes gift cards are being slow to arrive. The Google page has people who think the comments are the place to talk to Google support. A major outage will make itself known in far clearer ways.
- Buttons840 6y ago> Non-technical users misattribute and misunderstand causes of outages. The website simply answers the question "is anyone else having trouble accessing this?" In practice that's all it does, and that is useful.
- deathanatos 6y agoSure, but that doesn't prove the claim that was made: that several sites are experiencing a DNS DDoS attack. Occam's razor here, with the proof presented, is that people are misattributing the Azure outage.
- nonbirithm 6y agoMy broadband provider was down (Wave G) and had no status page. Social media was silent. The only way I could confirm it was an outage and not my local network setup was by using downdetector. I wish those companies would actually have status pages.
- bitcharmer 6y agoYou could also argue that it is still better than always-green status pages of cloud providers.
- partiallypro 6y agoThe problem with downdetector is that people say something is down when really it's another service. Like with Cloudflare, a lot of the comments are simply that a website was down giving an CF error, but in reality it was probably not CF that was down but an underlying service.
- feyman_r 6y agoAgree on the CF part. I found it interesting that the downdetector page had other cloud-providers like Google and AWS showing error spikes at around the same time.
- deleted 6y ago[deleted]
- foobiekr 6y agoOn the other hand, CF is themselves known for blaming the underlying site in their error pages when in fact the underlying wasn't the problem. So it's just a mess.
- dzhiurgis 6y agoI assume downdetector can isolate region, run a traceroute to at least at some extent analyse source of network issues?
- eurasiantiger 6y agoJust as DevOps thought of closing the lid for Easter. Nice.
- whoknew1122 6y agoAnecdotally, I've seen more DDoS customer tickets at AWS than I've ever seen.
- joenathanone 6y agoFrom my support ticket >As discussed, we found that your case could be part of a global scale incident wherein multiple Dynamics services were rendered inaccessible due to a suspected Azure DDoS attack. This issue started at approximately 21:30 UTC on 1st April 2021 and, along the symptoms, our customers may experience intermittent issues accessing Microsoft services, including Azure, Dynamics, and Power Automate. On this regard, the Microsoft teams involved have rerouted traffic to separate resilient DNS services and are seeing improvement in service availability. With this confirmation, as agreed, I will proceed to lower the severity of this case and transfer it for an agent working in your time zone to continue following up with you and confirm these services have returned to an expected operational state.