DoIT Outage History

We are investigating an issue affecting forecasting in Cloud Analytics. Some forecasts, as well as widgets and budgets that depend on forecasting, may fail to load or refresh and may display an error. Our engineering team is working to restore normal service. As a temporary workaround, customers may disable forecasting on affected reports where this option is available. We will provide another update when more information is available.

Summary Multi-product customers are experiencing elevated packet loss and errors. Affected products: Cloud Run, Google App Engine, Google Cloud Bigtable, Google Cloud Dataflow, Hybrid Connectivity, Virtual Private Cloud (VPC) Locations: zones/us-central1-b, zones/us-central1-b, zones/us-central1-b, zones/us-central1-b, zones/us-central1-b, zones/us-central1-bMore Details: Google is experiencing an issue with Hybrid Connectivity Tuesday, 2026-09-01 07:44 US/Pacific. Their engineering team is working to investigate the issue. More is expected later today. DCI Console features might be impacted by this outage.

See the Google Cloud status page for the most up-to-date details: https://status.cloud.google.com/incidents/j5ia5t9p3g9q5wi7r8ev

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 action is required at this time. Our team is actively monitoring the issue and reviewing the effect on DoiT notifications and related cost views. We will provide updates as we learn more from AWS and as impacted data stabilises.

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.

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.

We have identified an AWS data ingestion issue in DoiT Cloud Intelligence impacting consolidated resold customers, we will provide an update shortly

We are currently monitoring external GCP "Data delivery delays for Billing export to BigQuery." The team at Google is actively working on a resolution. Our team is tracking the situation closely and waiting for an update from GCP. We will provide an update as more information becomes available.

The team at Google is still working toward a resolution for the "Data delivery delays for Billing export to BigQuery" incident. We are continuing to monitor the situation closely. We will provide another update as soon as more information becomes available.

We are currently monitoring an external service event from AWS “AWS BILLING OPERATIONAL ISSUE” in us-east-1, which is impacting the accuracy of cost data. This AWS-side issue began on February 13, 2026, and affects Cost Explorer, the AWS Billing Console, and Cost and Usage Report (CUR) exports. Because the DoiT Console relies directly on these AWS data feeds, cost reports and dashboards for usage since February 1, 2026, may temporarily display incomplete, delayed, or zeroed-out values. AWS has confirmed they are in the process of regenerating cost data for all affected services to correct these discrepancies. Our team is tracking the situation closely and waiting for AWS to finalize their data regeneration. We will provide a follow-up update once AWS confirms that their billing exports are once again complete and accurate.

We have identified an issue affecting a subset of our public API traffic, resulting in errors or timeouts on some endpoints behind our external API gateway. Our team is working to identify the cause and restore functionality as quickly as possible.

We are investigating reports of errors when accessing Billing profiles in the DoiT Console. As a result, customers may be unable to view, create, or edit billing profiles. Our team is working to identify the cause and restore functionality as quickly as possible. Thank you for your patience and understanding.

We’re investigating reports that customers authenticating via Okta Single Sign-On (SSO) are unable to sign in to the DoiT console. Affected users may encounter a redirect loop back to the sign in page after attempting to sign in. Our engineering teams are actively investigating to identify the root cause and restore normal access. We’ll provide updates here as we learn more. Thank you for your patience, and we apologise for any inconvenience.

We are investigating an issue with a third‑party content delivery network that is causing intermittent failures and slow page loads in the DoiT Console. Some users may experience issues accessing the DoiT Console. Our team has engaged the provider and is working to restore normal performance.

We have detected and are investigating an issue where storage-related metrics in BigQuery Lens (for example, Storage price in the Explorer widget and related recommendations) may display inflated or otherwise incorrect values for some projects or datasets. Our engineering team is currently investigating the issue, and we appreciate your patience during this time.

We are continuing to investigate the issue. It appears the error originated from Cloudflare. You can track the status here: https://www.cloudflarestatus.com/

We are continuing to investigate this issue.

We are continuing to investigate this issue.