Update - Umbrella continue to monitor our input delays, currently it seems that AWS are catching up as most of currently running July invoices data is on the 18th. We will keep on monitoring for any issue. Latest update from AWS: We continue to make substantial progress toward resolving the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. Our mitigation efforts are working as expected and we are seeing an increasing number of accounts reflecting correct cost and usage data. We expect all affected accounts to be fully recovered by July 19, 12:00 AM PDT. Until the backfill is complete, some customers may still observe incorrect cost and usage data in the Billing and Cost Management Console and Cost and Usage Reports. These estimates do not reflect actual usage or charges. We will provide another update by July 18, 7:00 AM PDT, or sooner if additional information becomes available.
Jul 18, 2026 - 08:27 UTC
Monitoring - Note there is currently AWS billing issue at AWS. The umbrella processes and platform are fully operational during that period.
View the link from AWS describing the possible impact known right now.
Resolved -
The incident is resolved.
Jul 13, 15:58 UTC
Monitoring -
A fix was deployed and we are monitoring the outcome
Jul 13, 12:27 UTC
Identified -
Data updates to reseller customer users are stopped on July 9th. There is no data loss, this is only a display glitch. The issue has been identified and fix is being implemented.
Jul 13, 08:48 UTC
Resolved -
Issue was resolved on June 29th and the platform has resumed to full operational mode since.
Jul 6, 08:39 UTC
Update -
We are continuing to work on a fix for this issue.
Jun 29, 10:53 UTC
Identified -
Root cause of the issue has been identified, we're working on solution. Seems like no re-processing of data will be needed.
Jun 28, 11:22 UTC
Investigating -
We are currently investigating the issue, it does not look like a data availability nor missing issue but a mapping issue. We'll update once root cause is identified.
Jun 28, 09:43 UTC