SLA credits, outage runbooks, and cloud-cost recovery — the short version of everything we learn monitoring the big cloud providers.
August 12, 2026
The three acronyms on every provider SLA page mean different things. How AWS, Azure, GCP, and DigitalOcean define and measure downtime, and why the SLI is the clause that decides whether you get a credit.
Read moreAugust 11, 2026
Cloud SLA credits die on deadlines: 30 days for Google Cloud and DigitalOcean, about 60 for AWS and Azure, counted from the end of the month, not the incident. Exact windows from the current SLA pages plus a calendar routine that takes ten minutes a month.
Read moreAugust 10, 2026
Providers owe service credits after most major outages, yet almost nobody files. The four real blockers, who actually collects, and the deadlines that decide it.
Read moreAugust 10, 2026
When a client's cloud account has an outage, the provider owes a credit and the client will never file. IT providers can claim in under an hour: who can file on each provider, the exact windows, the evidence you already hold, and how the credit becomes a visible win.
Read moreAugust 9, 2026
How MSPs and IT providers can turn provider SLA credits into a client-facing service: who is allowed to file, the real deadlines, where the money lands, and pricing models that pay for the work.
Read moreAugust 7, 2026
Provider status pages lag real outages by 20 minutes or more and miss whole categories of incidents. What AWS, Azure, GCP and DigitalOcean status pages cover, what they hide, and why SLA credits never depend on them.
Read moreAugust 6, 2026
How to claim Azure SLA credits: reading Service Health correctly, the thresholds that trigger a credit, filing a refund request in the portal, and the two month deadline you cannot miss.
Read moreAugust 6, 2026
Published estimates put downtime at $15,000 per minute for large enterprises and $100,000 to $5 million per hour. How to calculate your own hourly number with revenue, payroll, and churn math, plus a worked example.
Read moreAugust 6, 2026
DigitalOcean's SLA is per product, not one document: Droplets at 99.99% per instance, Managed Databases from 99.5%, Spaces at 99.9%. Exact credit tiers, filing deadlines from 30 days to three months, and the 24-hour notice rule for Spaces.
Read moreAugust 6, 2026
Google Cloud owes you a financial credit when it breaches an SLA, but only if you file inside the window: 30 days for most services, 60 for Compute Engine. Exact windows, credit tiers, evidence, and the filing route.
Read moreAugust 5, 2026
The exact evidence AWS, Azure, Google Cloud, and DigitalOcean require in an SLA credit claim: request logs, timestamps, incident IDs, resource IDs, and the traps that get claims rejected.
Read moreAugust 4, 2026
Measure cloud outages with your own probes: check intervals, NTP time sync, and the monthly uptime math that decides whether an SLA credit claim exists. Exact threshold numbers included.
Read moreJuly 20, 2026
Cloud providers owe you service credits when they breach their uptime SLAs, but you have to ask. Step-by-step claim instructions, thresholds, and deadlines for AWS, Azure, Google Cloud, and DigitalOcean.
Read moreJuly 20, 2026
The exact AWS SLA credit tiers for EC2, S3, RDS, and Lambda, the 60-day claim deadline, what evidence AWS Support actually asks for, and a ready-to-submit claim template.
Read moreJuly 20, 2026
A 60-minute runbook for cloud outages: confirm it is really the provider, protect your systems, capture the evidence your SLA claim will need, and note the deadline before the postmortem fades.
Read more