AWS has found the root cause and is in the process of processing bills for all impacted customers. They are expecting that process to take a few hours. CloudHealth begins processing bills as soon as they are published, so we are anticipating reporting data for AWS to be up-to-date for all customers by 12PM EST Thursday November 13. We are continuing to monitor progress and remain in contact with AWS until the issue is fully resolved.
AWS has confirmed there is an issue on their end and we are working closely with them as they work to resolve the issue. We are seeing signs of improvement with some customer billing data coming through. We continue to keep in close contact with AWS as they work towards a full restore.
We are seeing signs of remediation and the bills are coming in for some customers. We are continuing to work with AWS to ensure the problem is completely resolved for all customers. We will provide updates as new information becomes available.
As per our initial investigation the issue seems to be occurring with Amazon Web Services (AWS). We have opened a priority ticket with AWS. A subset of customers may continue to experience incomplete cost/billing data.
We will provide updates as new information becomes available.
We are aware of an issue with AWS Cost data currently unavailable for a subset of customers.
Our engineering teams are engaged and currently investigating the issue. We will provide updates as more information becomes available.
We’ll find your subscription and send you a link to login to manage your preferences.
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
We’ll use your email to save your preferences so you can update them later.
Subscribe to other services using the bell icon on the subscribe button on the status page.
You’ll no long receive any status updates from Broadcom Service Status, are you sure?
{{ error }}
We’ll no longer send you any status updates about Broadcom Service Status.