Updated 24h ago
AWS vs Microsoft Azure SLA
Promised uptime per service, credits, support and what the status pages showed, side by side.
Change vendors (up to four; 2 picked)
VendorHighest SLAWith an SLAFastest support
Promise vs reality
ServiceDowntime vs allowed
Amazon DynamoDBAWS99.99% / 99.178%
Amazon EC2AWS99.99% / 99.178%
Amazon RDS (Multi-AZ)AWS99.95% / 99.178%
AWS LambdaAWS99.95% / 99.178%
Amazon BedrockAWS99.9% / 99.178%
Amazon S3 (Standard)AWS99.9% / 99.178%
Azure SQL DatabaseMicrosoft Azure99.995% / n/a
Azure Blob Storage (Storage Accounts)Microsoft Azure99.99% / n/a
Azure Virtual MachinesMicrosoft Azure99.99% / n/a
Azure FunctionsMicrosoft Azure99.95% / n/a
Azure OpenAI in Foundry ModelsMicrosoft Azure99.9% / n/a
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Best SLA by category
| Category | AWS | Microsoft Azure |
|---|---|---|
| Compute | 99.99%Amazon EC2 | 99.99%Azure Virtual Machines |
| AI models | 99.9%Amazon Bedrock | 99.9%Azure OpenAI in Foundry Models |
| Databases | 99.999%Amazon DynamoDB | 99.995%Azure SQL Database |
| Storage | 99.9%Amazon S3 (Standard) | 99.99%Azure Blob Storage (Storage Accounts) |
Support: fastest first response
Vendor and planFastestTargets
AWS Business Support+30 minBusiness-critical system down: < 30 mins · Production system down: < 1 hour · Production system impaired: < 4 hours · System impaired: < 12 hours · General guidance: < 24 hours
AWS Enterprise Support15 minBusiness/mission-critical system down: < 15 mins · Production system down: < 1 hour · Production system impaired: < 4 hours · System impaired: < 12 hours · General guidance: < 24 hours
AWS Unified Operations5 minMission-critical system down: < 5 mins from Incident Management Engineer · Production system down: < 1 hour · Production system impaired: < 4 hours · System impaired: < 12 hours · General guidance: < 24 hours
AWS Developer (legacy, closed to new subscriptions)n/aNo published response targets.
AWS Business (legacy, closed to new subscriptions)1 hCritical issues: 1 hour
AWS Enterprise On-Ramp (legacy, being deprecated)30 minCritical issues: 30 minutes
Microsoft Azure Basicn/aNo published response targets.
Microsoft Azure Developern/aMinimal business impact (Sev C): Within eight business hours
Microsoft Azure Standard1 hCritical business impact (Sev A): Within one hour · Moderate business impact (Sev B): Within four hours · Minimal business impact (Sev C): Within eight business hours
Microsoft Azure Professional Direct1 hCritical business impact (Sev A): Within one hour · Moderate business impact (Sev B): Within two hours · Minimal business impact (Sev C): Within four business hours
Microsoft Azure Unified Enterprise15 minCritical business system down (Sev 1): Within 15 mins for Azure, one hour for all other products · Critical business impact (Sev A): Within one hour · Moderate business impact (Sev B): Within two hours · Minimal business impact (Sev C): Within four business hours
Popular comparisons
Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.