SLA Credit Watch

Methodology

Data sources

Incidents are read from each vendor's own public status feed, polled every 3 minutes:

Every one of these is a public feed, and every one of them caps how far back its own history goes. Public incident history is an eligibility lead, not proof that a particular customer experienced contractual downtime. AWS Health RSS is terse, Azure RSS is interpreted conservatively, and Microsoft 365 is the public consumer feed rather than tenant-authenticated commercial Service Health.

Public-status math

We calculate automatic monthly uptime only where the published SLA makes the vendor's public status timeline part of the contractual calculation. In the current catalog that is Twilio's covered APIs:

uptime_pct = (minutes in month − outage minutes) / minutes in month

Month boundaries are UTC. Overlapping incidents affecting the same service and region are merged before their minutes are counted, so concurrent outages are not double-counted. Degraded-performance time is tracked and shown separately, but excluded from uptime_pct, because most SLAs define unavailability narrowly and do not credit degraded performance the way they credit an outage.

For AWS, Google Cloud, Azure, Microsoft 365 and Cloudflare, public incident minutes never enter a contractual ledger or trigger a claim. Their SLAs require customer account, plan, configuration, telemetry or impact data. Slack and Zoom standard published terms do not provide a numerical credit remedy, though a private agreement may differ.

Eligibility workflow

Every relevant incident links to a vendor-specific checklist. You may run the check yourself without providing contact information. If public data and your answers are not enough, you may separately and explicitly opt in to a free review from AllCaps Technologies. A review case is created only after that choice and contact consent.

Where the SLA rules come from

Every threshold, credit percentage, claim window, and filing channel on this site is encoded from that vendor's own live public terms, not from memory or a third-party summary. Each rule on a vendor page links its source, shows the verbatim quote it was taken from, and states the date it was verified.

Rules last verified Jul 09, 2026 to Jul 19, 2026.

Where a vendor's standard online terms carry no credit remedy for a service, its vendor page says so plainly rather than inventing one.

Public data

Every incident has a JSON endpoint at /i/{vendor}/{id}.json, and threshold-crossing events are published as an RSS feed at /events.rss. Both are free to cite with attribution to SLA Credit Watch (slacreditwatch.com).

What this site does not do

SLA Credit Watch does not give legal advice or guarantee vendor approval. Self-service results and AllCaps Technologies reviews assist with operational evidence, eligibility analysis and claim preparation; the vendor's own terms and validation control in every case.

Built and maintained by AllCaps Technologies.

Get outage alerts

When a selected vendor reports a relevant outage, we tell you what evidence to preserve and help you check eligibility. Use the checklist yourself, or optionally request a free review from AllCaps Technologies on the incident's eligibility page. Confirmed contractual alerts include the credit math and filing deadline.

Choose vendors, add your email, and confirm once. No spend or contract details required.