Flexera- Spot- All regions - Incorrect billing data for AWS customers

Update timeline

1. investigating Jul 17, 2026, 10:24 AM UTC

   Incident Description: We have identified an issue impacting billing and cost visibility for AWS customers in all regions. As a result of an active service provider disruption, customers may observe inaccurate, incomplete, or delayed estimated cost and usage information within the Billing and Cost Management Console. This issue is limited to AWS-based services and does not affect customers using other cloud platforms. Priority: P2 Restoration Activity: Our technical teams have confirmed that the issue is related to an active AWS service event affecting all regions. We are actively monitoring the situation and working closely with AWS updates to assess customer impact. Service restoration is dependent on AWS resolving the underlying issue, and we will continue to provide updates as additional information becomes available.

2. investigating Jul 17, 2026, 10:27 AM UTC

   We are continuing to investigate this issue.

3. identified Jul 17, 2026, 01:14 PM UTC

   We continue to closely monitor the service provider outage and its impact on affected services. Further updates will be provided as new information becomes available.

4. identified Jul 17, 2026, 06:24 PM UTC

   Our investigation and validation efforts to date have not identified any impact to Spot billing or cost analysis data. The billing and pricing data reviewed remains consistent with expected values. While initial validation results are positive, we are continuing additional validation activities as further data becomes available to confirm these findings. We remain engaged with AWS and will continue to monitor the situation closely. We will share additional updates as our validation activities continue.

5. identified Jul 18, 2026, 08:05 AM UTC

   We remain actively engaged with AWS and continue to closely monitor the situation. AWS has identified the root cause and implemented mitigation measures to address the underlying issue that resulted in incorrect estimated cost and usage data being displayed. AWS has begun backfilling data to restore accurate cost and usage information for all customers and full recovery is expected by 18 July 2026, 12:00 PM PDT.

6. monitoring Jul 18, 2026, 07:33 PM UTC

   We continue to monitor the AWS service event and remain engaged with AWS as they complete their recovery activities. Validation completed to date has not identified any impact to Spot billing or cost analysis data. We are continuing to monitor the situation and complete any remaining validation activities before determining closure of this incident.

7. resolved Jul 19, 2026, 12:59 PM UTC

   AWS resolved their service disruption on 18 July at 6:57 AM PDT. Following successful validation by our technical teams, we have confirmed that service functionality has been restored .

8. postmortem Jul 30, 2026, 06:10 PM UTC

   **Description:** Flexera Spot – AWS Billing Service Disruption Timeframe: July 17, 2026, 1:33 AM PDT – July 18, 2026, 6:57 AM PDT **Incident Summary** On July 17, 2026, at approximately 1:33 AM PDT, Flexera technical teams became aware of an AWS issue affecting estimated billing and usage data displayed within AWS Billing and Cost Management, Cost Explorer, and Cost and Usage Reports. Given the nature of the AWS service disruption, technical teams initiated an investigation to determine whether Spot billing, cost analysis, or savings calculations for AWS customers were affected. During the investigation, teams reviewed the billing and pricing data used by Spot, validated relevant cost and pricing tables, monitored AWS updates, and assessed whether any customer-facing billing or savings data had been impacted. Technical teams validated the billing and pricing data used by Spot and confirmed that the relevant cost and pricing tables were operating as expected. The investigation did not identify any issues within the data used by Spot, and no incorrect billing or savings calculations were observed. AWS subsequently confirmed that the issue originated within AWS Billing and Cost Management services, identified and mitigated the underlying issue, and completed data recovery and backfill activities. Based on the validation performed throughout the investigation, no customer impact was observed within Spot. Following confirmation of AWS recovery and completion of post-recovery validation activities, the incident was considered resolved. **Root Cause** The incident was caused by an AWS service issue affecting estimated billing and usage data displayed within AWS Billing and Cost Management, Cost Explorer, and Cost and Usage Reports. AWS identified and mitigated the underlying issue and completed data recovery activities. **Remediation Actions** The following actions were taken during the incident response: • Incident Investigation Initiated: Technical teams began investigating the AWS billing and usage data issue to determine whether Spot customers were affected. • Impact Assessment Performed: Technical teams evaluated whether the AWS service disruption affected Spot billing analysis and savings calculations. • Data Validation Completed: Teams reviewed and validated the billing and pricing data used by Spot and confirmed that relevant cost and pricing tables were operating as expected. • AWS Recovery Monitored: Technical teams monitored AWS communications, service updates, and recovery activities throughout the incident. • Post-Recovery Validation Performed: Additional validation was completed following AWS recovery and data backfill activities to confirm the integrity of billing and pricing data used by Spot. • Incident Resolved: The incident was closed after AWS confirmed recovery and technical validation identified no impact within Spot. **Future Preventative Measures** The following follow-up actions were identified during the incident: • AWS Collaboration and Review: Continue working closely with AWS to understand the underlying cause of provider-managed incidents and review any recommendations or learnings resulting from their investigation. • Resiliency and Validation Review: Review opportunities to further strengthen validation processes for billing-related data to support faster impact assessment and response during similar third-party service disruptions in the future.