Skip to main content

AWS vs Azure

Front door check counts, what each vendor’s status page recorded and SLA terms for these vendors.

30-day window ending

Front door checks

Every 15 minutes we send a request to a documented endpoint for each vendor from a single CheckUpstream location and count the answers. A reachable front door does not confirm that a customer action worked.

Front door check counts: AWS and Azure
Last 30 daysAWSAzure
Front door reachableOut of checks with a clear answer

No front door checks in this window

  • 2,253 of 2,253

    checks to management.azure.com

Checks 15 minutes apart cannot see disruptions shorter than that. Each vendor is checked at its own endpoints, so the counts cover different things.

AWS · check scope

No front door checks are recorded for this vendor in this window. That does not establish whether it was reachable.

View AWS record

Azure · check scope

  • management.azure.comapi · No vendor region

    Front door reachable in 2,253 of 2,253 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    5 more checks gave no clear answer and are not counted.

    First check in this window
    Latest clear answer
View Azure record

What each vendor’s status page says

Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.

Recorded incidents: AWS and Azure
Last 30 daysAWSAzure
Incidents recorded

4

0

Recorded incident durationMedian

Too few dated records

3 valid durations

Too few dated records

0 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded, as are records posted with one time for start and resolution. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.

AWS says

  • Increased Connectivity issues in US-EAST-1

    Started
    Closed in record
    Source incident
  • Elevated API issues and Launch Failures

    Started
    Closed in record
    Source incident
  • Elevated Launch Failures

    Started
    Closed in record
    Source incident

Azure says

No incidents recorded in this window. That does not establish an incident-free month.

Check the terms for your plan

An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.

AWS

8 public term records.

Bedrock (Standard models) · CloudFront · DynamoDB (Global Tables) · 5 more

Review AWS SLA guide

Azure

No public terms recorded here.

Review Azure SLA guide