Looking for an update now? Check the current status, or follow DoiT International for future changes.
91.9%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
90%
30
3
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
Cost anomalies showing stale excess cost and status
A fix has been implemented and we are monitoring the results.
identified
Some cost anomalies in the console are showing outdated excess cost and status values. Detection is unaffected — anomalies are still being created — but the job that updates them is failing partway through, so the excess cost shown can be well below actual spend. Cost reports and billing data are unaffected. We have identified the cause and a fix is in progress.
Legacy Incident Archive
6 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
AWS billing data issue causing inaccurate cost signals in DoiT Cloud Intelligence
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Recovery is now underway for the AWS billing data issue. While the backfill is still in progress, we are closely monitoring the situation, validating our data, and making any necessary adjustments on our side.
Thank you for your patience and understanding.
investigating
We are investigating the impact of an AWS incident affecting estimated billing and cost data.
Due to incorrect estimated billing values reported by AWS, some customers may see false or misleading cost anomaly notifications in DoiT Cloud Intelligence. This may also affect cost-related experiences that rely on AWS estimated billing data, including Budgets, Alerts, and DCI Analytics.
AWS has stated that the displayed billing estimates do not reflect actual usage or charges and that no customer a...
June 2026
General issue with opening GCP Expert Inquiry tickets from the DCI Console
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been resolved, and our team is actively monitoring the results to make sure everything is working as expected.
identified
The issue has been identified, and a fix is being implemented.
investigating
We are currently investigating an issue impacting Google Cloud ticket submissions in the DCI Console. When attempting to open a ticket, the required GCP Project field displays no available options, preventing successful submission.
If you are blocked by this issue and need to submit an urgent request, please select DoiT Console as the Cloud Platform and provide the full details of your request in the body of the ticket.
May 2026
Investigating incorrect April AWS cost data for some CloudHealth-managed customers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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.
identified
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.
investigating
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 ...
AWS missing data
Source not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been identified, and a fix is being implemented.
investigating
We have identified an AWS data ingestion issue in DoiT Cloud Intelligence impacting consolidated resold customers, we will provide an update shortly
April 2026
AWS missing data
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor AWS data ingestion in DoiT Cloud Intelligence. We have observed a recurrence of ingestion issues affecting a subset of customers. Customers whose AWS accounts are managed via CloudHealth on shared payer accounts may experience delayed or incomplete AWS cost data due to an upstream issue in CloudHealth.
Data for other customers remains up to date, and we are closely monitoring all ingestion pipelines and working with CloudHealth to restore normal operation.
monitoring
We have implemented a fix for the AWS ingestion problem in DoiT Cloud Intelligence. The data for affected customers has been updated, and we are actively monitoring the ingestion pipeline to ensure stability.
identified
We have identified an issue affecting AWS customers regarding missing data
March 2026
Intermittent AWS ingestion issue affecting subset of DCI customers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The AWS data ingestion is currently working as expected. Our Engineering Team is continuing to monitor to ensure the issue is fully resolved. We will update further as the resolution is fully confirmed.
monitoring
We have deployed a fix to address the AWS ingestion issue in DCI. The impacted customers’ data has now been updated, and we are closely monitoring the ingestion pipeline to ensure it remains stable and no further impact occurs.
identified
We have identified a problem with AWS data ingestion. Some customers are facing issues with AWS cost and usage data in DoiT Cloud Intelligence, while others are unaffected.
Impacted tenants are experiencing delayed or missing AWS data in analytics and dashboards. We are actively working to identify the scope of the issue and are developing remediation steps simultaneously. Thank you for your understanding during this time.