Conversation

Notices

1. Embed this notice
   Kevin Beaumont (gossithedog@cyberplace.social)'s status on Tuesday, 30-Jul-2024 23:04:08 JST Kevin Beaumont

   lol the Azure status page just refreshed and all the locations in America are written in Chinese for some reason. Caching, maybe.

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Tuesday, 30-Jul-2024 23:39:19 JST Kevin Beaumont

     in reply to

     Looks like Azure is back. 2 hours 30 minutes 🫡

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 00:24:16 JST Kevin Beaumont

     in reply to

     Apparently Meris are DDoS’ing Azure today

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 00:51:57 JST Kevin Beaumont

     in reply to

     Time to bring back the classic? 🤣 https://cyberplace.social/@GossiTheDog/110563950845439264

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 03:28:23 JST Kevin Beaumont

     in reply to

     Just to be explicitly clear about this, there is an ongoing DDoS attack aimed at Azure. They’re using similar language to last time this happened in 2023.

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 03:45:05 JST Kevin Beaumont

     in reply to

     I've written about how Microsoft need to be transparent about customer impacting denial of service attacks. https://doublepulsar.com/microsoft-need-to-be-transparent-about-customer-impacting-ddos-attacks-763a9c0d46ef

   • Embed this notice
     Miss Aemilia🎀 (missaemilia@mastodon.gamedev.place)'s status on Wednesday, 31-Jul-2024 07:50:13 JST Miss Aemilia🎀

     in reply to

     @GossiTheDog They do need to be more transparent, but they're not going to be. This is the culture as a whole, invented by AWS. You never call it an outage, and you never engage transparently, weasel your way out of every ~service interruption~ and ~heightened API error rates~. Why? Because if you transparently acknowledge outages and failures, you have to pay out more SLAs.

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 17:13:26 JST Kevin Beaumont

     in reply to

     Microsoft have now said this was a DDoS attack.

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 17:35:53 JST Kevin Beaumont

     in reply to

     What is Azure Front Door? https://learn.microsoft.com/en-us/azure/frontdoor/front-door-ddos

   • Embed this notice
     Kevin Beaumont (gossithedog@cyberplace.social)'s status on Wednesday, 31-Jul-2024 17:42:16 JST Kevin Beaumont

     in reply to

     Yesterdays impact beyond Azure:

   • Embed this notice
     Tobias Frech (tobiasfrech@ijug.social)'s status on Wednesday, 31-Jul-2024 18:34:26 JST Tobias Frech

     in reply to

     @GossiTheDog wow, that should free up some large portions of IT budget now. I mean, you don't need to hire big corp anymore if you can point at this and say "Even big MS with their Azure cloud could not defend against a DDoS!"