Cloud outages can create a short, evidence-heavy path to a service-credit request. I trace the exact service-specific SLA, organize your sanitized incident and billing evidence, identify missing requirements and deadline risks, and prepare a factual support-ticket outline for you to review and submit through your own provider account.

You receive: • A provider, service, billing-channel, and agreement trace • An incident evidence matrix • A claim-deadline card with the official source • A prerequisite and exclusion screen • A nonbinding planning calculation when the published terms and affected charge are clear • A factual client-submitted support-ticket outline • One 30-minute findings call and one written clarification round

The screen covers one AWS, Microsoft Azure, or Google Cloud provider; up to three client-identified incidents; and up to five affected services or resources. It uses only client-authorized, redacted material. No credentials, console access, customer data, payment data, raw databases, or unredacted production logs are needed.

This is operational evidence organization, not a provider decision, claim filing, outage verification, legal or contract interpretation, cloud engineering, or accounting advice. I do not contact the provider or promise eligibility, approval, recovery, refunds, cash payment, savings, or outcomes. The exact current provider agreement controls.