Flexera incident

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

Major Resolved View vendor source →

Flexera experienced a major incident on July 17, 2026 affecting Spot UI, lasting 2d 2h. The incident has been resolved; the full update timeline is below.

Started
Jul 17, 2026, 10:24 AM UTC
Resolved
Jul 19, 2026, 12:59 PM UTC
Duration
2d 2h
Detected by Pingoru
Jul 17, 2026, 10:24 AM UTC

Affected components

Spot UI

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 .