DoIT incident

Investigating incorrect April AWS cost data for some CloudHealth-managed customers

Minor Resolved View vendor source →

DoIT experienced a minor incident on May 18, 2026 affecting Cloud Cost Analytics and Dashboards and 1 more component, lasting 40d 20h. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 01:05 PM UTC
Resolved
Jun 28, 2026, 09:12 AM UTC
Duration
40d 20h
Detected by Pingoru
May 18, 2026, 01:05 PM UTC

Affected components

Cloud Cost AnalyticsDashboardsBilling

Update timeline

  1. investigating May 18, 2026, 01:05 PM UTC

    We are investigating a recurrence of a CloudHealth-related issue affecting April AWS cost data and assessing the impact on April invoices for multiple customers. Some customers may see inaccurate or otherwise inflated April charges in DoiT Cloud Intelligence. Our current checks indicate that the values shown in DoiT match the data currently available in CloudHealth, and we are working with CloudHealth to confirm scope and resolution steps. We will share another update as soon as we have more information.

  2. identified May 20, 2026, 09:14 AM UTC

    CloudHealth has identified the affected customers and is currently updating their billing data. We are continuing to closely monitor their progress. Once CloudHealth confirms the data update is complete, we will review the results on our side and share a further update. Thank you for your patience and understanding.

  3. identified May 26, 2026, 06:46 AM UTC

    CloudHealth has advised that they have implemented a fix for this issue, and we are now monitoring and validating the outcome on our side. At this time, we are reviewing the data on our side to verify its integrity. We will share a further update once this validation is complete. Thank you for your patience and understanding.

  4. monitoring May 27, 2026, 01:47 PM UTC

    CloudHealth has advised that they have implemented a fix for this issue and updated the affected data. We are now monitoring the data to ensure everything continues to behave as expected. We appreciate your continued patience while we complete these checks.

  5. resolved Jun 28, 2026, 09:12 AM UTC

    CloudHealth’s fix has been validated on our side, and we have confirmed that the affected April AWS cost data has been corrected. At this time, the issue is resolved, and we are no longer seeing unexpected behavior related to this incident. Thank you for your patience and understanding while we worked through the investigation, remediation, and validation process with CloudHealth.