VMware Tanzu CloudHealth: AWS Cost/Usage Data Issue

Resolved
Resolved

Data for May 2024 has been reprocessed.

Note for Partners: Due to manual historical billing re-runs, a small percentage of large channel customers may still see delays in statements and reports until tomorrow, but the re-run is in process and will update once complete.

Monitoring

We still have a small subset of impacted customers. However, we are making steady progress and will continue to refresh and monitor costs over the weekend.

Monitoring

We have verified most impacted customers have had their data restored. However, there is still a subset of customers that we expect to have their data restored once the next data refresh completes later today.

Monitoring

Backfilling has restored missing May 30, and May 31, 2024 data for the majority of impacted customers, but there is a subset of customers that are still in the process of being backfilled.

We expect that these customers should have May 2024 Cost data restored following the next data refresh cycle.

Monitoring

A fix has been implemented and cost/usage files have been refreshed for impacted customers. We are currently monitoring, but expect May reports to be backfilled by tomorrow morning.

Identified

We have identified the cause of the issue that has led to delays in May 30th and May 31st 2024 data availability in Cost and Usage Reporting.

We are working on a fix for the issue now, but don't expect this to to impact June 2024 Cost and Usage Reporting. We are in the process of backfilling Cost and Usage Reporting for May 2024 for impacted customers currently. We will provide updates as new information becomes available.

Investigating

We continue to investigate the issue. We will provide updates once new information becomes available.

Investigating

We are currently investigating an issue with VMware Tanzu CloudHealth. The cost/usage report data for May 30 and 31, 2024 is currently partial or missing for AWS customers.

Our engineering teams are engaged and actively investigating the issue. We will provide updates as more information becomes available.

Began at:

Affected components
  • VMware Cloud Services
    • VMware Tanzu
      • VMware Tanzu CloudHealth
        • AWS Data
        • Azure Data
        • Google Cloud Data
        • Oracle Cloud Data
        • Data Center