AWS publishes 8 product-level uptime commitments. When a commitment is missed, the credit tiers below apply to that product's monthly charges, but only if you file a claim within 60 days. These are the same terms CheckUpstream measures against when it tracks your entitlement.
Commitment: 99.9% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.9% | 10% |
| below 99% | 25% |
| below 95% | 100% |
Scheduled maintenance excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.9% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.9% | 10% |
| below 99% | 25% |
| below 95% | 100% |
Scheduled maintenance excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.999% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.999% | 10% |
| below 99.9% | 25% |
| below 99% | 100% |
Scheduled maintenance excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.99% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.99% | 10% |
| below 99% | 30% |
| below 95% | 100% |
Scheduled maintenance excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.99% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.99% | 10% |
| below 99% | 30% |
| below 95% | 100% |
Scheduled maintenance excluded. Single-AZ impact excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.95% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.95% | 10% |
| below 99% | 30% |
| below 95% | 100% |
Scheduled maintenance excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.95% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.95% | 10% |
| below 99% | 30% |
| below 95% | 100% |
Scheduled maintenance excluded. Single-AZ impact excluded. Terms effective since Jan 1, 2024. Vendor source ↗
Commitment: 99.9% uptime per calendar month · file within 60 days from the end of the billing month
| Monthly uptime | Service credit |
|---|---|
| below 99.9% | 10% |
| below 99% | 25% |
| below 95% | 100% |
Scheduled maintenance excluded. Terms effective since Jan 1, 2024. Vendor source ↗
AWS commits to 99.9%–99.999% uptime across 8 tracked product-level commitments. A credit is owed only when measured uptime for the affected product falls below its target for the measurement window — the per-product targets and credit tiers are listed above.
AWS requires the vendor's own status-page entry for the incident, your AWS account ID, the affected region, the affected resource ARNs, failed request IDs. Claims without the required evidence are routinely denied — collect it before you file.
The shortest filing window across AWS's tracked terms is 60 days, counted from the end of the billing cycle in which the breach occurred. Miss the deadline and the credit is forfeit — vendors do not file on your behalf.
Open a case in the AWS Support Center (account & billing category) and paste your evidence into the case body. Reference the incident window, the affected product, and the credit tier you're claiming.
Credits are owed, not offered
Vendors don't file these claims for you. CheckUpstream measures AWS uptime against the commitments above, computes what a breach is worth on your actual spend, and drafts the claim before the filing window closes.
Track your AWS entitlement →AWS's tracked credit tiers range from 10% to 100% of the affected product's monthly charges, depending on how deep the breach was.