![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 85%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
3,201 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 40%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@Scott Pisciotta
Mitigated- Azure Storage Blob SFTP service encountered availability issues in East US
What happened?
Between 18:16 UTC on 25 March 2025 and 05:21 UTC on 26 March 2025, a platform issue resulted in Azure Blob Storage SFTP connections getting blocked and timing out. Customers may have experienced failures when attempting to connect via SFTP to some Azure Storage Account resources in East US region.
What do we know so far?
We determined that some Azure Storage Blob SFTP customers in East US region experienced availability issues due to connections getting blocked and timing out.
How did we respond?
Storage service nodes were restarted to mitigate, and additional recent configuration changes were rolled back out of an abundance of caution until the comprehensive RCA is completed.
What happens next?
To request a Post Incident Review (PIR), impacted customers can use the “Request PIR” feature within Azure Service Health.
To get notified if a PIR is published, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts .
For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs .
The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring .
Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness
If the answer helped (pointed you in the right direction) > please click Accept Answer. which might be beneficial to other community members reading this thread. And, if you have any further queries do let us know.