Microsoft Azure Outage Map
The map below depicts the most recent cities worldwide where Microsoft Azure users have reported problems and outages. If you are having an issue with Microsoft Azure, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Microsoft Azure users affected:
Check Current Status
E-mail
Microsoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.
Check Current Status
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Los Angeles, CA | 1 |
| New Delhi, NCT | 1 |
| Muscat, Muḩāfaz̧at Masqaţ | 1 |
| New York City, NY | 1 |
| Mississauga, ON | 1 |
| Oritor, Northern Ireland | 1 |
| Loja, Provincia de Loja | 1 |
| São Paulo, SP | 1 |
| Uniontown, PA | 1 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Microsoft Azure Issues Reports
Latest outage, problems and issue reports in social media:
-
🤯
(@forlayo) reported
@davidhine99 @BleepinComputer @Azure It wasn’t http connections but regular tcp connections to a port that’s not 80 or 443 but a higher one in which my service is residing; all those connections came without negotiating tls. So it looks more like a scan or just an attack of opening connections to that port. I doubt it’s a DNS issue, and I doubt what happened with Azure yesterday was a DNS issue… I believe that’s being an “easy” answer when a big cloud ****** up hard
-
Michael Akin
(@MichaelJAkin) reported
@JamesSampica @Azure Interestingly, it showed AWS down at the same time
-
Akebono
(@Akeb0n0) reported
@Azure servers down??
-
🤯
(@forlayo) reported
@BleepinComputer Today, during the @Azure service disruption we had several waves of hundreds different addresses reaching us thousands of times each 10 minutes as some type of attack.. and we got it on a Linux machine we’ve hosted in Azure.. I believe it can’t be casual, maybe what had happened isn’t exactly what’s being “explained“.
-
heardof_ai
(@heardof_ai) reported
@frictionfounder @Azure @Bayer Actually, not yet. Private LLMs help compliance, but data is the bottleneck. Today: yield models ~10–20% MAPE, sparse field telemetry, rural connectivity <50% in many regions. No audited evals/red‑teams. Use for ops/comms, not autonomous agronomy. Watch RCTs: >5% yield or <10% inputs.
-
C J TEJA SAI
(@cjtejasai) reported
Anyone know reason for @Microsoft @Azure outage? 🤔🤔🤔🤔
-
Rajeev
(@RajeevCinema) reported
So first @awscloud and now @Azure -- all down? Seriously, what will AI do if clouds are unreliable?
-
🤯
(@forlayo) reported
Today, during the @Azure service disruption we had several waves of hundreds different addresses reaching us thousands of times each 10 minutes as some type of attack.. and we got it on a Linux machine we’ve hosted in Azure.. I believe it can’t be casual, maybe what have happened isn’t exactly what’s being “explained“
-
Leah Stern
(@LeahBStern) reported
My 4 year old is pissed @Minecraft that you’re not working. @Azure pls get it back up and running or all hell is going to break loose.
-
Rough Neck
(@NoHezitetion) reported
What just happened.....I have never seen Azure services load this fast in Africa @Azure @Microsoft365
-
lightchild
(@lightchilduk) reported
@DougMadory @Azure No way, it has never worked for me.
-
Samuel Le Pajolec
(@SamuelLePajolec) reported
@Azure I need to open a Severity 1/A ticket, but the phone support is unreachable. Please let me know the process to follow as soon as possible !
-
Vinnie Pinzone
(@phantomdistress) reported
We initiated deployment of our ‘last known good’ configuration, which has now been completed. Customer configuration changes will remain blocked while we continue mitigation efforts. At this stage, we anticipate full mitigation within the next 4 hours. @microsoft @Azure
-
GomezUndercover
(@Gm_Undercover) reported
@Azure Bet it would make shareholders mad if you guys actually admitted and acknowledge the outage huh, the ***** to release this and then just have the whole thing backfire is so funny.
-
WellKnitTech
(@WellKnitTech) reported
@DougMadory @Azure IOW it was so broken they didn’t know how to fix it or there are no reliable engineers left to fix it because they laid off the ones that could.
Check Current Status