CloudHealth - Discrepancy with AWS monthly data being displayed for July 2026

We have monitored the service for stability and this incident shall now be closed.

AWS has confirmed that bills have been corrected for the majority of their customers by 6:00 AM PDT (13:00 UTC) July 18. CloudHealth began reprocessing bills and reports for impacted customers at that time and have confirmed that costs have been corrected once the report generation cycle completes. We expect costs to be fully refreshed and corrected for all customers by 6:00 PM PDT (01:00 UTC) July 19 or sooner.

AWS has reported that backfills are progressing but are taking longer than anticipated. Their new ETA for all customers to have corrected billing data is 12:00 AM PDT (07:00 UTC) July 19. CloudHealth will reprocess all impacted customers at that time and expects all customers to have corrected cost data in reports by 12:00 AM PDT (07:00 UTC) July 20 or sooner.

We will provide further updates as necessary and/or when data has been updated.

AWS has determined the root cause of the inflated costs and is in the process of backfilling impacted customers. Their current ETA for a full restore is 12:00 PM PDT (19:00 UTC) July 18. CloudHealth will begin reprocessing customer data at this time and expects reports to be updated with the latest corrected data by 7:00 AM PDT (14:00 UTC) July 19 or sooner.

We will provide further updates as necessary and/or when data has been corrected.

AWS Customers logging into Cloudhealth will notice an inflated cost for the month of July 2026.

This is caused by an upstream issue with the AWS Billing and Cost Management Console.

The CloudHealth engineering team is closely monitoring the situation as AWS works toward a resolution.