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,879 of 2,879

    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,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    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

2

6

Recorded incident durationMedian

Too few dated records

1 valid duration

5h 1m

6 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded. 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

  • [RESOLVED] Elevated packet loss

    Started
    Closure
    Not recorded
    Source incident

  • [RESOLVED] Increased Error Rates

    Started
    Closed in record
    Source incident
All AWS reportsVendor status page

Azure says

  • Active - ExpressRoute Gateway - Multiple services experiencing connectivity issues in multiple regions

    Started
    Closed in record
    Source incident

  • Active - Azure ExpressRoute Gateway service impacting event in multiple Azure Regions

    Started
    Closed in record
    Source incident

  • Active - Multiple services experiencing connectivity issues in multiple regions

    Started
    Closed in record
    Source incident
All Azure reportsVendor status page

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