If you build or run systems, you already know the shape of a concentrated control plane: a change goes out globally, the health signal looks fine, and then the failure shows up everywhere at once. Microsoft’s recent public incident reviews describe that shape in official language. This note takes those reviews at their word, adds the Cyber Safety Review Board’s 2024 report on Storm-0558, and then describes — from internetcomputer.org documentation — how the Internet Computer is built, and what Qerron actually does on top of it.
Two cautions up front. First, the mid-November 2026 Microsoft 365 incident did not yet have a published Post Incident Review at the time of writing; what we have is Microsoft’s own service health text. Second, an outage is not an intrusion. The Storm-0558 case is included because official reviews of it speak directly to identity and signing keys, which are part of the same concentration problem.
What Microsoft has said about the latest incident, and about earlier ones.
Under incident MO1550821, Microsoft’s service health updates recorded a start time of 18:26 UTC on 12 November 2026, with users possibly unable to connect to multiple Microsoft 365 services. In an update at 17:57 UTC on 13 November 2026, Microsoft apologized, reported broad recovery and stability, and said the event was a technical issue, introduced by an issue during an earlier network capacity upgrade that surfaced after a recent network change. It said it had addressed the underlying issue, was still restoring remaining customers and regions, and would publish a full post-incident report once its review was complete. As of that update, status was still listed as service degradation, and the formal root-cause field was still “N/A.” Those updates are Microsoft’s, as collected in a public extract of Microsoft 365 admin-center incident reports. Microsoft listed Exchange Online access failures — Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync, and REST — and delayed mail as part of the impact. It also stated that most core Microsoft Teams functions, including calls, meetings, group chats, and channel messages, were not impacted, while scenarios that depend on Exchange Online were.
A completed review is available for the Azure Front Door incident of 29–30 October 2025, tracking ID YKYN-BWZ. Microsoft says that between 15:41 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services using Azure Front Door and Azure CDN saw connection timeouts and DNS failures. The stated cause is precise enough to be useful: a sequence of valid, non-malicious customer configuration changes, made across two control-plane build versions, produced incompatible metadata. That metadata exposed a latent data-plane bug. Because the crash was asynchronous, the configuration protection system received healthy signals and let the change propagate to a majority of edge sites; the last-known-good snapshot was updated with the bad configuration as well. Microsoft listed a long set of affected Azure services, and also Microsoft 365 (MO1181369), parts of Microsoft Entra ID, the Azure Portal, and the ability to open support cases.
The 2–3 February 2026 PIR, tracking ID FNJ8-VQZ, is a control-plane story. Microsoft says a remediation workflow intended to disable anonymous access on Microsoft-managed storage accounts was, because of a data-synchronization defect in targeting logic, applied to accounts that VM extension packages have to read. Impact on virtual machines and dependent services ran from 18:03 UTC on 2 February to about 00:30 UTC on 3 February, across multiple regions. Restoring access then produced a retry storm that saturated managed identities in East US and West US until 06:05 UTC. Automatic retries, Microsoft wrote, amplified load faster than added capacity could absorb it.
Storm-0558, in the terms Microsoft and the CSRB used.
In July 2023, Microsoft described how Storm-0558, which it assessed as a China-based actor with espionage objectives, used forged authentication tokens to access customer email, beginning 15 May 2023, at approximately 25 organizations and related consumer accounts. The Cyber Safety Review Board’s report of 20 March 2024, citing Microsoft, gives later figures: 22 enterprise organizations and 503 related personal accounts worldwide, including at least 391 personal accounts in the United States, and names senior U.S. officials whose mailboxes were accessed.
The mechanism, as both Microsoft and the Board describe it, combined two failures. A Microsoft account consumer signing key from 2016 was used to sign tokens. Exchange Online’s token validation did not enforce issuer and scope checks that would have rejected a consumer key for an enterprise mailbox. Microsoft’s 6 September 2023 investigation post, later updated on 12 March 2024, said a consumer signing system crash in April 2021 produced a crash dump, that a race condition had allowed key material to be present (a point Microsoft later narrowed: it had not found a crash dump containing the impacted key), and that the leading hypothesis remained operational errors that let key material leave the secure token signing environment, later accessed from a debugging environment through a compromised engineering account. Separately, Microsoft said mail systems started using a common key-metadata endpoint in 2022, and that developers incorrectly assumed helper libraries performed complete scope validation.
The Board concluded the intrusion was preventable and “should never have occurred,” and that it succeeded because of “a cascade of security failures at Microsoft.” It called signing keys “the cryptographic equivalent of crown jewels,” and wrote that, combined with the validation flaw, the stolen key “permitted Storm-0558 to gain full access to essentially any Exchange Online account anywhere in the world.” It also recorded Microsoft’s full cooperation, and criticized the time it took Microsoft to correct inaccurate public statements. Those are the Board’s words. The useful engineering point is the blast radius of a signing key and of a missing validation check — and how much of the internet’s mail sits behind both.
How the Internet Computer is built.
Official ICP documentation is the right primary source here. The Internet Computer is a network of independent blockchains called subnets. Each subnet runs its own instance of the protocol stack — peer-to-peer, consensus, message routing, and execution — and hosts canisters, which are WebAssembly programs with their own state. A canister lives on one subnet and is replicated across every node of that subnet. Docs state that a single node cannot unilaterally change a canister’s state.
Nodes are physical machines running replica software. They are owned by independent node providers, voted into the network by the Network Nervous System, under a process the docs call deterministic decentralization: subnet membership is designed to be diverse across operators, geographies, and jurisdictions. You deploy to a subnet; you do not pick a single host.
Consensus on each subnet produces one finalized block per round, about every second, with cryptographic rather than probabilistic finality. Once an update call returns, the state change is committed. Query calls are different: they skip consensus and are handled by a single node, which is why official docs say they carry weaker authenticity guarantees unless the canister uses certified variables.
Chain-key cryptography is the threshold layer underneath. Each subnet has one public key. No individual node holds the corresponding private key. The key is split into shares and distributed across the subnet. Nodes produce signature shares and combine them without reconstructing the full key. Official docs describe threshold BLS for ICP’s internal operations — consensus, response certification, cross-subnet messaging, randomness — and chain-key signatures (threshold ECDSA and Schnorr) for signing on other chains. Verifying a subnet’s output is a check of one signature against one public key.
Qerron also uses vetKeys, which ICP documentation describes as verifiable encrypted threshold key derivation. In the product, items are encrypted on the device with vetKeys threshold encryption before they are stored, so we cannot read them, and no single server can either.
None of this is a claim that the protocol is unhackable, or that a single subnet cannot have problems. It is a claim about the failure domain: there is no single company control plane whose configuration, or whose signing-key environment, is the only place the vault lives.
What Qerron actually is, in that architecture.
Qerron is a passkey vault. The frontend and backend are canisters. Sign-in is a passkey through Internet Identity; there is no master password, and we do not keep a password database of ours to leak. You can share a vault with a one-time invite link, and set a named-person check-in for access if you cannot open it. It is not a will, not legal advice, and not a custodian. It is not a substitute for Microsoft 365. It is a place to keep logins, notes, and recovery details on this network, with a 14-day trial and no credit card required. Personal is $48 a year. Household is $72 a year.
A shorter, less technical companion is when Outlook goes down. A version written for business owners and IT is Microsoft 365 went down again. The earlier note that started this thread is When Microsoft goes down, half the internet goes with it. For the protocol itself, start with the network overview.
Sources
- Microsoft service health updates for incident MO1550821, as recorded in the University of Pennsylvania’s public extract of Microsoft 365 admin-center incident reports: mailservices.isc.upenn.edu/computing/email/penno365/alerts/ms-incidents.html
- Microsoft Azure PIR YKYN-BWZ, Azure Front Door, 29–30 October 2025: azure.status.microsoft/en-us/status/history/?trackingId=YKYN-BWZ
- Microsoft Azure PIR FNJ8-VQZ, virtual machines and managed identities, 2–3 February 2026: azure.status.microsoft/en-us/status/history/?trackingId=FNJ8-VQZ
- Microsoft Threat Intelligence, “Analysis of Storm-0558 techniques for unauthorized email access,” 14 July 2023: microsoft.com/en-us/security/blog/2023/07/14/analysis-of-storm-0558-techniques-for-unauthorized-email-access/
- Microsoft Security Response Center, “Results of Major Technical Investigations for Storm-0558 Key Acquisition,” 6 September 2023, updated 12 March 2024: microsoft.com/en-us/msrc/blog/2023/09/results-of-major-technical-investigations-for-storm-0558-key-acquisition
- Cyber Safety Review Board, “Review of the Summer 2023 Microsoft Exchange Online Intrusion,” 20 March 2024: cisa.gov/resources-tools/resources/CSRB-Review-Summer-2023-MEO-Intrusion
- ICP docs: Network overview, Protocol stack, Consensus, Chain-key cryptography, Canisters, VetKeys
Try it free for 14 days, no credit card needed.