Skip to content

Outage tracker / Microsoft Azure

Is Microsoft Azure down?

I'm having a problem

Vendor reports no incidentWhat Microsoft Azure reports

Microsoft Azure reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:33 UTC.

Microsoft Azure's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Microsoft Azure pass from all 10 regions we check.

As of Nov 5, 2026, 2:33 PM UTC, RealUptime's checks of Microsoft Azure passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:33 PM UTC
US-East540 msChecks passing
US-West508 msChecks passing
Europe167 msChecks passing
Asia-Pacific724 msChecks passing
US-Central785 msChecks passing
Canada206 msChecks passing
UK319 msChecks passing
Southeast Asia651 msChecks passing
Australia1392 msChecks passing
South America1603 msChecks passing
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 Nov 5, 2026, 2:27 PM UTC
Microsoft Azure's own status page shows no incident, and our checks of Microsoft Azure pass 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
1.2sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 466ms2026-10-08 UTC: p95 414ms2026-10-09 UTC: p95 408ms2026-10-10 UTC: p95 389ms2026-10-11 UTC: p95 337ms2026-10-12 UTC: p95 386ms2026-10-13 UTC: p95 432ms2026-10-14 UTC: p95 485ms2026-10-15 UTC: p95 487ms2026-10-16 UTC: p95 406ms2026-10-17 UTC: p95 849ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 728ms2026-10-20 UTC: p95 867ms2026-10-21 UTC: p95 870ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 749ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 857ms2026-10-28 UTC: p95 862ms2026-10-29 UTC: p95 848ms2026-10-30 UTC: p95 939ms2026-10-31 UTC: p95 995ms2026-11-01 UTC: p95 854ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
1.5sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 371ms2026-10-08 UTC: p95 484ms2026-10-09 UTC: p95 375ms2026-10-10 UTC: p95 385ms2026-10-11 UTC: p95 378ms2026-10-12 UTC: p95 433ms2026-10-13 UTC: p95 607ms2026-10-14 UTC: p95 479ms2026-10-15 UTC: p95 365ms2026-10-16 UTC: p95 359ms2026-10-17 UTC: p95 832ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 939ms2026-11-02 UTC: p95 958ms2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Europe
841msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 331ms2026-10-08 UTC: p95 315ms2026-10-09 UTC: p95 253ms2026-10-10 UTC: p95 296ms2026-10-11 UTC: p95 290ms2026-10-12 UTC: p95 341ms2026-10-13 UTC: p95 254ms2026-10-14 UTC: p95 242ms2026-10-15 UTC: p95 264ms2026-10-16 UTC: p95 212ms2026-10-17 UTC: p95 414ms2026-10-18 UTC: p95 964ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 606ms2026-10-21 UTC: p95 525ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 751ms2026-10-24 UTC: p95 742ms2026-10-25 UTC: p95 733ms2026-10-26 UTC: p95 724ms2026-10-27 UTC: p95 753ms2026-10-28 UTC: p95 791ms2026-10-29 UTC: p95 815ms2026-10-30 UTC: p95 733ms2026-10-31 UTC: p95 758ms2026-11-01 UTC: p95 842ms2026-11-02 UTC: p95 836ms2026-11-03 UTC: p95 632ms2026-11-04 UTC: p95 725ms2026-11-05 UTC: p95 841ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.7sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 864ms2026-10-08 UTC: p95 787ms2026-10-09 UTC: p95 766ms2026-10-10 UTC: p95 718ms2026-10-11 UTC: p95 668ms2026-10-12 UTC: p95 746ms2026-10-13 UTC: p95 745ms2026-10-14 UTC: p95 834ms2026-10-15 UTC: p95 841ms2026-10-16 UTC: p95 794ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
US-Central
1.1sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 656ms2026-10-08 UTC: p95 545ms2026-10-09 UTC: p95 541ms2026-10-10 UTC: p95 557ms2026-10-11 UTC: p95 522ms2026-10-12 UTC: p95 605ms2026-10-13 UTC: p95 594ms2026-10-14 UTC: p95 612ms2026-10-15 UTC: p95 601ms2026-10-16 UTC: p95 593ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 883ms2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 935ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 529ms2026-10-08 UTC: p95 435ms2026-10-09 UTC: p95 604ms2026-10-10 UTC: p95 551ms2026-10-11 UTC: p95 518ms2026-10-12 UTC: p95 531ms2026-10-13 UTC: p95 509ms2026-10-14 UTC: p95 528ms2026-10-15 UTC: p95 451ms2026-10-16 UTC: p95 446ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 999ms2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 982ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
UK
945msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 475ms2026-10-08 UTC: p95 410ms2026-10-09 UTC: p95 429ms2026-10-10 UTC: p95 403ms2026-10-11 UTC: p95 333ms2026-10-12 UTC: p95 499ms2026-10-13 UTC: p95 413ms2026-10-14 UTC: p95 440ms2026-10-15 UTC: p95 423ms2026-10-16 UTC: p95 411ms2026-10-17 UTC: p95 709ms2026-10-18 UTC: p95 884ms2026-10-19 UTC: p95 950ms2026-10-20 UTC: p95 952ms2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 726ms2026-10-26 UTC: p95 726ms2026-10-27 UTC: p95 923ms2026-10-28 UTC: p95 807ms2026-10-29 UTC: p95 928ms2026-10-30 UTC: p95 867ms2026-10-31 UTC: p95 806ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 849ms2026-11-04 UTC: p95 893ms2026-11-05 UTC: p95 945ms
Oct 7Oct 21Nov 5
Southeast Asia
1.8sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 760ms2026-10-08 UTC: p95 633ms2026-10-09 UTC: p95 759ms2026-10-10 UTC: p95 842ms2026-10-11 UTC: p95 594ms2026-10-12 UTC: p95 689ms2026-10-13 UTC: p95 816ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 646ms2026-10-16 UTC: p95 730ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 656ms2026-10-08 UTC: p95 666ms2026-10-09 UTC: p95 608ms2026-10-10 UTC: p95 673ms2026-10-11 UTC: p95 627ms2026-10-12 UTC: p95 695ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 808ms2026-10-15 UTC: p95 675ms2026-10-16 UTC: p95 626ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 3.0s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
1.7sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 749ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 933ms2026-10-11 UTC: p95 654ms2026-10-12 UTC: p95 650ms2026-10-13 UTC: p95 800ms2026-10-14 UTC: p95 688ms2026-10-15 UTC: p95 698ms2026-10-16 UTC: p95 804ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 6.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.6s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Microsoft Azure

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Microsoft Azure reports an incident on its status page, and again when it reports it resolved.

Get an email when Microsoft Azure reports an incident

Email me when Microsoft Azure reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Microsoft Azure's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 540msstatus code: 401checked: Nov 5, 2026, 2:31 PM 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
      Checks passinglatency: 508msstatus code: 401checked: Nov 5, 2026, 2:32 PM 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
      Checks passinglatency: 785msstatus code: 401checked: Nov 5, 2026, 2:33 PM 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
      Checks passinglatency: 206msstatus code: 401checked: Nov 5, 2026, 2:30 PM 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
    Checks passinglatency: 1603msstatus code: 401checked: Nov 5, 2026, 2:31 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 167msstatus code: 401checked: Nov 5, 2026, 2:31 PM 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
      Checks passinglatency: 319msstatus code: 401checked: Nov 5, 2026, 2:30 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 724msstatus code: 401checked: Nov 5, 2026, 2:32 PM 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
      Checks passinglatency: 651msstatus code: 401checked: Nov 5, 2026, 2:33 PM 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
      Checks passinglatency: 1392msstatus code: 401checked: Nov 5, 2026, 2:31 PM 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 probe events

Network Connectivity – Gateway service degradation in multiple regions, 5h 45mdeclared on their status page2026-09-30
Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services – Intermittent request failures and latency in Sweden Central, 5h 55mdeclared on their status page2026-09-29
Network connectivity – Issues accessing resources in West US, 4h 57mdeclared on their status page2026-07-23
Azure OpenAI Service – Latency and intermittent failures in multiple regions, 7h 26mdeclared on their status page2026-05-29
Multiple services – Power/cooling issues in West US 2, 22h 6mdeclared on their status page2026-05-29
Multiple services – Control plane issues in East US, 11h 52mdeclared on their status page2026-04-24
Azure OpenAI – GPT-5.2 availability degradation in 7 regions, 20h 12mdeclared on their status page2026-03-09
Power event impacting multiple services – West US, 20h 26mdeclared on their status page2026-02-07

check 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 check readings and Microsoft Azure's own claim at the time, side by side.

Full check history for Microsoft Azure: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Microsoft Azure uptime by RealUptime's checksLive, from this page's own readings.
[![Microsoft Azure uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Microsoft Azure down?", https://realuptime.io/outages/azure. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: auth surface
https://management.azure.com/subscriptions?api-version=2020-01-01
secondary
https://azure.status.microsoft/en-us/status

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: management.azure.com

RealUptime is not affiliated with Microsoft Azure; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.