Skip to content

Outage tracker / Microsoft Azure

Is Microsoft Azure down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Microsoft Azure from all 10 regions we check.

As of Sep 23, 2026, 9:10 AM UTC, Microsoft Azure answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Microsoft Azure (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:10 AM UTC
US-East398 msOperational
US-West212 msOperational
Europe383 msOperational
Asia-Pacific444 msOperational
US-Central402 msOperational
Canada221 msOperational
UK256 msOperational
Southeast Asia514 msOperational
Australia230 msOperational
South America222 msOperational
their status pagetheir claim, not our reading

Microsoft Azure reports: All systems operational (“No open events reported”)

from Microsoft Azure's own status page, checked Sep 23, 2026, 8:47 AM UTC
Our probes and Microsoft Azure's own status page agree: both show Microsoft Azure as reachable right now.

This is Microsoft Azure's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Microsoft Azure response time, by region

US-East
375msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 503ms2026-08-26 UTC: p95 448ms2026-08-27 UTC: p95 519ms2026-08-28 UTC: p95 492ms2026-08-29 UTC: p95 509ms2026-08-30 UTC: p95 446ms2026-08-31 UTC: p95 451ms2026-09-01 UTC: p95 582ms2026-09-02 UTC: p95 549ms2026-09-03 UTC: p95 468ms2026-09-04 UTC: p95 478ms2026-09-05 UTC: p95 388ms2026-09-06 UTC: p95 399ms2026-09-07 UTC: p95 375ms2026-09-08 UTC: p95 397ms2026-09-09 UTC: p95 346ms2026-09-10 UTC: p95 433ms2026-09-11 UTC: p95 401ms2026-09-12 UTC: p95 396ms2026-09-13 UTC: p95 375ms2026-09-14 UTC: p95 388ms2026-09-15 UTC: p95 426ms2026-09-16 UTC: p95 471ms2026-09-17 UTC: p95 486ms2026-09-18 UTC: p95 476ms2026-09-19 UTC: p95 455ms2026-09-20 UTC: p95 410ms2026-09-21 UTC: p95 410ms2026-09-22 UTC: p95 447ms2026-09-23 UTC: p95 375ms
Aug 25Sep 8Sep 23
US-West
361msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 807ms2026-08-26 UTC: p95 792ms2026-08-27 UTC: p95 531ms2026-08-28 UTC: p95 474ms2026-08-29 UTC: p95 430ms2026-08-30 UTC: p95 429ms2026-08-31 UTC: p95 390ms2026-09-01 UTC: p95 380ms2026-09-02 UTC: p95 420ms2026-09-03 UTC: p95 503ms2026-09-04 UTC: p95 410ms2026-09-05 UTC: p95 488ms2026-09-06 UTC: p95 383ms2026-09-07 UTC: p95 402ms2026-09-08 UTC: p95 412ms2026-09-09 UTC: p95 385ms2026-09-10 UTC: p95 418ms2026-09-11 UTC: p95 361ms2026-09-12 UTC: p95 253ms2026-09-13 UTC: p95 333ms2026-09-14 UTC: p95 281ms2026-09-15 UTC: p95 345ms2026-09-16 UTC: p95 362ms2026-09-17 UTC: p95 393ms2026-09-18 UTC: p95 378ms2026-09-19 UTC: p95 356ms2026-09-20 UTC: p95 360ms2026-09-21 UTC: p95 352ms2026-09-22 UTC: p95 366ms2026-09-23 UTC: p95 361ms
Aug 25Sep 8Sep 23
Europe
278msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 297ms2026-08-26 UTC: p95 345ms2026-08-27 UTC: p95 273ms2026-08-28 UTC: p95 382ms2026-08-29 UTC: p95 376ms2026-08-30 UTC: p95 353ms2026-08-31 UTC: p95 421ms2026-09-01 UTC: p95 448ms2026-09-02 UTC: p95 457ms2026-09-03 UTC: p95 450ms2026-09-04 UTC: p95 464ms2026-09-05 UTC: p95 423ms2026-09-06 UTC: p95 379ms2026-09-07 UTC: p95 390ms2026-09-08 UTC: p95 304ms2026-09-09 UTC: p95 299ms2026-09-10 UTC: p95 337ms2026-09-11 UTC: p95 325ms2026-09-12 UTC: p95 276ms2026-09-13 UTC: p95 259ms2026-09-14 UTC: p95 324ms2026-09-15 UTC: p95 285ms2026-09-16 UTC: p95 300ms2026-09-17 UTC: p95 294ms2026-09-18 UTC: p95 328ms2026-09-19 UTC: p95 312ms2026-09-20 UTC: p95 311ms2026-09-21 UTC: p95 312ms2026-09-22 UTC: p95 337ms2026-09-23 UTC: p95 278ms
Aug 25Sep 8Sep 23
Asia-Pacific
690msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 646ms2026-08-26 UTC: p95 708ms2026-08-27 UTC: p95 572ms2026-08-28 UTC: p95 763ms2026-08-29 UTC: p95 720ms2026-08-30 UTC: p95 733ms2026-08-31 UTC: p95 771ms2026-09-01 UTC: p95 814ms2026-09-02 UTC: p95 946ms2026-09-03 UTC: p95 904ms2026-09-04 UTC: p95 729ms2026-09-05 UTC: p95 675ms2026-09-06 UTC: p95 649ms2026-09-07 UTC: p95 620ms2026-09-08 UTC: p95 714ms2026-09-09 UTC: p95 725ms2026-09-10 UTC: p95 679ms2026-09-11 UTC: p95 693ms2026-09-12 UTC: p95 705ms2026-09-13 UTC: p95 633ms2026-09-14 UTC: p95 620ms2026-09-15 UTC: p95 628ms2026-09-16 UTC: p95 686ms2026-09-17 UTC: p95 745ms2026-09-18 UTC: p95 783ms2026-09-19 UTC: p95 743ms2026-09-20 UTC: p95 743ms2026-09-21 UTC: p95 720ms2026-09-22 UTC: p95 771ms2026-09-23 UTC: p95 690ms
Aug 25Sep 8Sep 23
US-Central
588msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 728ms2026-09-04 UTC: p95 654ms2026-09-05 UTC: p95 706ms2026-09-06 UTC: p95 644ms2026-09-07 UTC: p95 688ms2026-09-08 UTC: p95 708ms2026-09-09 UTC: p95 770ms2026-09-10 UTC: p95 799ms2026-09-11 UTC: p95 637ms2026-09-12 UTC: p95 655ms2026-09-13 UTC: p95 686ms2026-09-14 UTC: p95 615ms2026-09-15 UTC: p95 692ms2026-09-16 UTC: p95 641ms2026-09-17 UTC: p95 580ms2026-09-18 UTC: p95 591ms2026-09-19 UTC: p95 589ms2026-09-20 UTC: p95 579ms2026-09-21 UTC: p95 601ms2026-09-22 UTC: p95 611ms2026-09-23 UTC: p95 588ms
Aug 25Sep 8Sep 23
Canada
447msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 419ms2026-09-04 UTC: p95 507ms2026-09-05 UTC: p95 603ms2026-09-06 UTC: p95 623ms2026-09-07 UTC: p95 566ms2026-09-08 UTC: p95 634ms2026-09-09 UTC: p95 643ms2026-09-10 UTC: p95 551ms2026-09-11 UTC: p95 486ms2026-09-12 UTC: p95 480ms2026-09-13 UTC: p95 507ms2026-09-14 UTC: p95 494ms2026-09-15 UTC: p95 578ms2026-09-16 UTC: p95 460ms2026-09-17 UTC: p95 419ms2026-09-18 UTC: p95 446ms2026-09-19 UTC: p95 484ms2026-09-20 UTC: p95 440ms2026-09-21 UTC: p95 425ms2026-09-22 UTC: p95 487ms2026-09-23 UTC: p95 447ms
Aug 25Sep 8Sep 23
UK
526msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 453ms2026-09-04 UTC: p95 390ms2026-09-05 UTC: p95 353ms2026-09-06 UTC: p95 462ms2026-09-07 UTC: p95 385ms2026-09-08 UTC: p95 474ms2026-09-09 UTC: p95 288ms2026-09-10 UTC: p95 414ms2026-09-11 UTC: p95 395ms2026-09-12 UTC: p95 359ms2026-09-13 UTC: p95 394ms2026-09-14 UTC: p95 239ms2026-09-15 UTC: p95 289ms2026-09-16 UTC: p95 250ms2026-09-17 UTC: p95 291ms2026-09-18 UTC: p95 276ms2026-09-19 UTC: p95 276ms2026-09-20 UTC: p95 285ms2026-09-21 UTC: p95 537ms2026-09-22 UTC: p95 563ms2026-09-23 UTC: p95 526ms
Aug 25Sep 8Sep 23
Southeast Asia
928msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 763ms2026-09-04 UTC: p95 810ms2026-09-05 UTC: p95 703ms2026-09-06 UTC: p95 689ms2026-09-07 UTC: p95 813ms2026-09-08 UTC: p95 764ms2026-09-09 UTC: p95 591ms2026-09-10 UTC: p95 651ms2026-09-11 UTC: p95 717ms2026-09-12 UTC: p95 607ms2026-09-13 UTC: p95 572ms2026-09-14 UTC: p95 655ms2026-09-15 UTC: p95 709ms2026-09-16 UTC: p95 787ms2026-09-17 UTC: p95 794ms2026-09-18 UTC: p95 822ms2026-09-19 UTC: p95 836ms2026-09-20 UTC: p95 757ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1s2026-09-23 UTC: p95 928ms
Aug 25Sep 8Sep 23
Australia
818msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 849ms2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 921ms2026-09-06 UTC: p95 717ms2026-09-07 UTC: p95 616ms2026-09-08 UTC: p95 586ms2026-09-09 UTC: p95 546ms2026-09-10 UTC: p95 705ms2026-09-11 UTC: p95 721ms2026-09-12 UTC: p95 749ms2026-09-13 UTC: p95 659ms2026-09-14 UTC: p95 778ms2026-09-15 UTC: p95 786ms2026-09-16 UTC: p95 574ms2026-09-17 UTC: p95 585ms2026-09-18 UTC: p95 592ms2026-09-19 UTC: p95 728ms2026-09-20 UTC: p95 608ms2026-09-21 UTC: p95 699ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 818ms
Aug 25Sep 8Sep 23
South America
754msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 893ms2026-09-04 UTC: p95 951ms2026-09-05 UTC: p95 1.0s2026-09-06 UTC: p95 788ms2026-09-07 UTC: p95 678ms2026-09-08 UTC: p95 789ms2026-09-09 UTC: p95 835ms2026-09-10 UTC: p95 763ms2026-09-11 UTC: p95 883ms2026-09-12 UTC: p95 853ms2026-09-13 UTC: p95 788ms2026-09-14 UTC: p95 788ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 692ms2026-09-17 UTC: p95 735ms2026-09-18 UTC: p95 574ms2026-09-19 UTC: p95 594ms2026-09-20 UTC: p95 705ms2026-09-21 UTC: p95 673ms2026-09-22 UTC: p95 534ms2026-09-23 UTC: p95 754ms
Aug 25Sep 8Sep 23

Is it Microsoft Azure, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Microsoft Azure -- it cannot diagnose Microsoft Azure's own systems.

What we measured, function by function

Microsoft Azure answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 398msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Microsoft Azure normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 212msstatus code: 401checked: Sep 23, 2026, 9:10 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Microsoft Azure normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 402msstatus code: 401checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Microsoft Azure normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 221msstatus code: 401checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Microsoft Azure normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 222msstatus code: 401checked: Sep 23, 2026, 9:10 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Microsoft Azure normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 383msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Microsoft Azure normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 256msstatus code: 401checked: Sep 23, 2026, 9:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Microsoft Azure normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 444msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Microsoft Azure normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 514msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Microsoft Azure normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 230msstatus code: 401checked: Sep 23, 2026, 9:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Microsoft Azure normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Microsoft Azure, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Microsoft Azure yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Microsoft Azure.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Microsoft Azure since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Microsoft Azure covering any window you pick, with our measurements and Microsoft Azure's own claim at the time, side by side.

Full availability history for Microsoft Azure: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Microsoft Azure, and again when they can reach it again. That is our own measurement from ten regions, not Microsoft Azure's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Microsoft Azure uptime measured by RealUptimeLive, from this page's own readings.
[![Microsoft Azure uptime measured by RealUptime](https://realuptime.io/outages/azure/badge.svg?days=30)](https://realuptime.io/outages/azure)
<a href="https://realuptime.io/outages/azure"><img src="https://realuptime.io/outages/azure/badge.svg?days=30" alt="Microsoft Azure uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Microsoft Azure's SLA implies, from our measurement

At or above your target

We measured none of downtime for Microsoft Azure over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Microsoft Azure's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://management.azure.com/subscriptions?api-version=2020-01-01
secondary
https://azure.status.microsoft/en-us/status
RealUptime is not affiliated with Microsoft Azure; the name identifies what we measured, and nothing here speaks for Microsoft Azure's own team. We send a single web request to Microsoft Azure from 10 regions on our own schedule and time the response. We do not see inside Microsoft Azure's systems, do not use an account or real transaction, and are not the same signal Microsoft Azure's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Microsoft Azure is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.