Discover · purdue.edu

No picture published by purdue.edu

New Myths for Old

{weblog_name} purdue.edu

On Thursday, November 12, Microsoft 365, the company’s cloud suite for mail, meetings, and documents, began to fail. Outlook mail went first, and the failure spread to Teams, SharePoint, Copilot, and parts of Microsoft’s security tooling. Within about an hour, Downdetector (a site that tallies user reports of outages) had reports from 74 countries and territories. As I write on Friday, the outage is in its second day. Unity Health Toronto declared a “Code Grey” for loss of infrastructure. The outage reached the NHS, the Scottish Parliament, and Police Scotland, and it disrupted government systems in Singapore and Japan.

Microsoft says there is “no indication this is the result of malicious or cyber activity.” On Thursday afternoon (U.S. Eastern), it reported finding no recent change that matched the start of the trouble. An hour later, it was examining several configuration updates, and that evening it began reverting a network configuration change that did match. By its account, the process that establishes secure connections was overwhelmed, and servers stopped handling requests. It has not said that the change was the cause, and it has published no root cause.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

In the piece

Named in it

aljazeera.com74 countries and territoriesaljazeera.comcp24.comdeclared a “Code Greycp24.comsciencemediacentre.orgthe NHS, the Scottish Parliament, and Police Scotlandsciencemediacentre.orgabcnews.com“no indication this is the result of malicious or cyber activity.abcnews.comcloudadminhub.coma network configuration change that did matchcloudadminhub.comsecuritymagazine.comdismissed its memberssecuritymagazine.comgov.ukthe UKgov.ukBing Mapsthe EUmicrosoft.comABC Newsinvoked a resilience agreementabc.net.ausocradar.ioMicrosoft’s incident notice · in 1. Are you treating this as a security problem?socradar.ioTenable News Feed1,093 vulnerabilities · in 2. Whom are you depending on?tenable.comsplashtop.comOctober’s 1,413 · in 2. Whom are you depending on?splashtop.comtheregister.comnearly ten hours · in 2. Whom are you depending on?theregister.comthousandeyes.comtook down Azure Front Door · in 2. Whom are you depending on?thousandeyes.comhttps://www.engadget.com/denial-of-service attacks · in 2. Whom are you depending on?engadget.comCybersecurity and Infrastructure Security Agency CISAThe CSRB concluded · in 2. Whom are you depending on?cisa.govcyberscoop.comSecure Future Initiative · in 2. Whom are you depending on?cyberscoop.comschneier.com“CyberInsecurity: The Cost of Monopoly. · in 2. Whom are you depending on?schneier.comitsfoss.commoving off the platform · in 2. Whom are you depending on?itsfoss.comThe Next Webthe connectors linking ChatGPT and Claude to Microsoft 365 · in 3. What do your AI agents do when their vendors are unreachable?thenextweb.commarketscale.comall went down for hours · in 3. What do your AI agents do when their vendors are unreachable?marketscale.comookla.comOokla analysis of U.S. Downdetector data · in 3. What do your AI agents do when their vendors are unreachable?ookla.com

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from {weblog_name}

  1. Single Point of Everything; 4 Important Questionspurdue.edu
  2. Invoice Enclosedpurdue.edu
  3. More Than the Codepurdue.edu
  4. After the Buggy Whippurdue.edu
  5. Ph.D.s in Cybersecuritypurdue.edu
  6. Ch-ch-ch-changespurdue.edu