Azure Cosmos DB - East US
At a glance · Microsoft's status
ResolvedLasted 19 h 11 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 12:30 UTC on 4 Jan 2022. Microsoft marked it resolved at 07:41 UTC on 5 Jan 2022 after 19 h 11 min. Microsoft has since published a post-incident report.
Microsoft says
Microsoft's latest update, , in short excerpts.
Summary of Impact: Between 12:30 UTC on 04 Jan 2022 and 7:41 UTC on 5 Jan 2022, customers with Azure Cosmos DB accounts in East…
Timeline
Times in UTC, Microsoft's own where it gives them.
4 Jan 2022
MicrosoftMicrosoft says it startedon Azure Status
5 Jan 2022+19 h 11 min
MicrosoftResolved
13 Nov+1774 days 2 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