Virtual Machines - West US - Resolved
At a glance · Microsoft's status
ResolvedLasted 1 h 52 min
- Microsoft says it started
- · on Azure Status
- Earliest version we archived
- · our archive started 15:10 UTC
- Ended
- · marked resolved
- Edited
- Not since we first saw it
- Source
- Azure Status · checked 6 min ago
In short
Microsoft reported degraded service affecting Azure, starting 04:38 UTC on 12 Feb 2022. Microsoft marked it resolved at 06:30 UTC after 1 h 52 min. Microsoft has since published a post-incident report.
Microsoft says
Microsoft's latest update, , in short excerpts.
Impact Statement: Between 04:38 UTC and 6:30 UTC on 12 Feb 2022, you were identified as a customer using Virtual Machines, Azure SQL and Storage…
Timeline
Times in UTC, Microsoft's own where it gives them.
12 Feb 2022
MicrosoftMicrosoft says it startedon Azure Status
+1 h 52 min
MicrosoftResolved
13 Nov+1735 days 10 h
MicrosoftEarliest version we archivedOur archive started 15:10 UTC; earlier versions were not recorded.
What Microsoft changed
Microsoft rewrites incident updates in place. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full current text is on Microsoft's page.
One version so far. If Microsoft edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: Post-incident report
- Status
- Post-incident report
Seen by us · Microsoft's page
Last updated