This historical advisory concerns the October 20, 2025 AWS service event. It is not a current claim-filing notice. Any deadline depends on the applicable service agreement and billing period.
Investigate the cost impact
Review affected resource IDs, error metrics, usage records, retry behavior, and failover activity. Separate ordinary usage from incident-related changes; do not assume every spike qualifies for a service credit.
Apply the correct service agreement
AWS's Amazon Compute SLA distinguishes a qualifying region-level EC2 deployment from a single instance. The region-level commitment generally covers instances deployed concurrently across multiple Availability Zones in the same region; it is not a blanket benefit for any multi-region architecture.
Under the published EC2 schedule checked September 17, 2026, a qualifying monthly uptime percentage of 98% falls in the 30% credit tier, not 10%. This is an illustrative reading of that tier, not a determination that a particular workload qualifies. The applicable service, monthly calculation, exclusions, claim evidence, and contract govern eligibility.
Submit evidence through AWS Support
Use the process and time limit in the agreement that applied to the incident. Include the affected resources, periods of unavailability, and supporting logs. Separate questions about retry or failover charges from an SLA claim: additional credits or refunds are not guaranteed.
Verify the outcome
Track the support decision and any credit applied to the eligible bill. Reconcile the result with your invoice and address unexplained differences through the support case.
PointFive can help teams investigate cost anomalies and resource context. It cannot determine contractual eligibility or promise reimbursement from a cloud provider.