Fabric customers may have experienced delays or intermittent access issues due to increased request traffic impacting part of the infrastructure.
At a glance · Microsoft's status
ResolvedListed for 6 h 22 min
- First posted
- on the Fabric support page
- Ended
- · marked resolved
- Affects
- Microsoft Fabric
- Edited
- Not since we first saw it
- Source
- Microsoft Fabric support · checked 1 min ago
In short
Microsoft reported degraded service affecting Microsoft Fabric, first posted on the Fabric support page at 14:37 UTC on 18 May. Microsoft marked it resolved at 21:00 UTC, 6 h 22 min after it was first posted.
Microsoft says
Microsoft's latest update, , in short excerpts.
Fabric customers may have experienced delays or intermittent access issues due to increased request traffic impacting part of the infrastructure.
Timeline
Times in UTC, Microsoft's own where it gives them.
18 May
MicrosoftFirst public post (version 1)
+6 h 22 min
MicrosoftResolved
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: Resolved · 1 service
- Status
- Resolved
- Services
- Microsoft Fabric
Seen by us · Microsoft's page
Affected services
Changes around this incident
Possible connection
Changes to the same services that took effect shortly before the incident started. A shared service and time is not evidence that the change caused it.
- Fabric Activator alert ingestion failing due to metric ownership mismatch · Fabric and Power BI known issues · Same service; published 15 hours before it started ()
Last updated