<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Doit incidents — Vendor Status Watch</title><link>https://approjects-vendor-status-watch.static.hf.space/v/doit.html</link><description>Incidents from Doit's public status page, polled daily.</description><lastBuildDate>Wed, 16 Sep 2026 12:28:20 +0000</lastBuildDate><item><title>Cost anomalies showing stale excess cost and status [resolved]</title><link>https://stspg.io/t2smyw9rnqj3</link><guid isPermaLink="false">doit:2026-09-11T11:19:10.357Z</guid><pubDate>Fri, 11 Sep 2026 11:19:10 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Google Cloud issue [ONGOING]: Multiple Google Cloud services [resolved]</title><link>https://stspg.io/93kmzd7qgtdj</link><guid isPermaLink="false">doit:2026-09-01T16:07:30.027Z</guid><pubDate>Tue, 01 Sep 2026 16:07:30 +0000</pubDate><description>Google has resolved the incident and all components should be operational.</description></item><item><title>AWS billing data issue causing inaccurate cost signals in DoiT Cloud Intelligence [resolved]</title><link>https://stspg.io/lgymyy4v1gfs</link><guid isPermaLink="false">doit:2026-07-17T10:13:45.786Z</guid><pubDate>Fri, 17 Jul 2026 10:13:45 +0000</pubDate><description>The AWS billing data issue has now been resolved.

We have validated the recovery and confirmed that the affected cost data has stabilised. Related cost views and notifications in DoiT Cloud Intelligence should now reflect normal behaviour. 

Thank you for your patience and understanding throughout this incident.</description></item><item><title>General issue with opening GCP Expert Inquiry tickets from the DCI Console [resolved]</title><link>https://stspg.io/2fdv13g839ln</link><guid isPermaLink="false">doit:2026-06-26T23:12:00.098Z</guid><pubDate>Fri, 26 Jun 2026 23:12:00 +0000</pubDate><description>The incident has been resolved. All systems are operating normally.</description></item><item><title>Investigating incorrect April AWS cost data for some CloudHealth-managed customers [resolved]</title><link>https://stspg.io/f9g4j2s41zgh</link><guid isPermaLink="false">doit:2026-05-18T13:05:58.331Z</guid><pubDate>Mon, 18 May 2026 13:05:58 +0000</pubDate><description>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.</description></item><item><title>AWS missing data [resolved]</title><link>https://stspg.io/f2fz2vhgdflw</link><guid isPermaLink="false">doit:2026-05-08T11:49:18.445Z</guid><pubDate>Fri, 08 May 2026 11:49:18 +0000</pubDate><description>We are pleased to confirm that the AWS data ingestion issue in DoiT Cloud Intelligence, impacting consolidated resold customers, has now been resolved.
All affected data ingestion workflows are operating normally again.
Thank you for your patience and understanding while our teams worked to address this issue.</description></item><item><title>AWS missing data [resolved]</title><link>https://stspg.io/49flqb92slqd</link><guid isPermaLink="false">doit:2026-04-06T13:39:22.894Z</guid><pubDate>Mon, 06 Apr 2026 13:39:22 +0000</pubDate><description>We have fully resolved the AWS data ingestion issues in DoiT Cloud Intelligence, including those impacting customers with AWS accounts managed via CloudHealth on shared payer accounts. Data is now populating as expected for affected customers, and ingestion pipelines are operating normally.</description></item><item><title>Intermittent AWS ingestion issue affecting subset of DCI customers [resolved]</title><link>https://stspg.io/4pyldcz12hp2</link><guid isPermaLink="false">doit:2026-03-27T12:02:52.344Z</guid><pubDate>Fri, 27 Mar 2026 12:02:52 +0000</pubDate><description>The AWS ingestion issue in DoiT Cloud Intelligence has been resolved, and the affected data has been updated. Thank you for your patience.</description></item><item><title>AWS missing data [resolved]</title><link>https://stspg.io/ck4y55ptrvqc</link><guid isPermaLink="false">doit:2026-03-26T09:58:34.757Z</guid><pubDate>Thu, 26 Mar 2026 09:58:34 +0000</pubDate><description>We have fixed the issue and expect data to be updated in your DCI console within the next few hours</description></item><item><title>GCP Data Delivery Delays for billing exports to BigQuery [resolved]</title><link>https://stspg.io/xtfnfx0hxqw2</link><guid isPermaLink="false">doit:2026-03-06T16:26:59.032Z</guid><pubDate>Fri, 06 Mar 2026 16:26:59 +0000</pubDate><description>Google has confirmed that the underlying issue causing delays in GCP Billing exports to BigQuery has been fixed, and data delivery has returned to normal. 
Our team has verified that recent billing data is being delivered successfully and does not expect further impact from this incident. We appreciate your patience and understanding.</description></item><item><title>Inaccurate AWS Cost Data [resolved]</title><link>https://stspg.io/lvfbyvtpzvf8</link><guid isPermaLink="false">doit:2026-02-16T19:43:33.140Z</guid><pubDate>Mon, 16 Feb 2026 19:43:33 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Delayed GCP data delivery of cost and usage since February 11, 2026 [resolved]</title><link>https://stspg.io/y8kprx9qykrp</link><guid isPermaLink="false">doit:2026-02-16T08:31:36.724Z</guid><pubDate>Mon, 16 Feb 2026 08:31:36 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Delayed GCP cost and usage data updates since January 10, 2026 [resolved]</title><link>https://stspg.io/hngczfyqkrr5</link><guid isPermaLink="false">doit:2026-01-13T12:26:15.687Z</guid><pubDate>Tue, 13 Jan 2026 12:26:15 +0000</pubDate><description>We have completed ingestion of the Google Cloud Platform (GCP) billing exports and are now seeing GCP cost and usage data fully up to date in the DoiT Console and Cloud Analytics. Our monitoring confirms that data freshness and completeness have returned to normal. We apologize for any inconvenience and appreciate your patience and understanding while we worked through this upstream issue.</description></item><item><title>Subset of public APIs are unavailable [resolved]</title><link>https://stspg.io/1b52691bcxb1</link><guid isPermaLink="false">doit:2026-01-03T00:02:49.315Z</guid><pubDate>Sat, 03 Jan 2026 00:02:49 +0000</pubDate><description>This incident has been resolved. Public APIs continue to operate normally and our monitoring has not detected any further issues. No additional customer impact is expected.</description></item><item><title>Sign-in via Magic Link Unavailable [resolved]</title><link>https://stspg.io/97wtzknp52r0</link><guid isPermaLink="false">doit:2025-12-11T12:23:13.311Z</guid><pubDate>Thu, 11 Dec 2025 12:23:13 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Billing profiles unavailable in DoiT Console [resolved]</title><link>https://stspg.io/s928mjqn33vq</link><guid isPermaLink="false">doit:2025-12-08T14:15:42.908Z</guid><pubDate>Mon, 08 Dec 2025 14:15:42 +0000</pubDate><description>Access to Billing profiles in the DoiT console has been fully restored, and all services are operating as expected. We appreciate your understanding and thank you for your patience while our team worked to resolve this issue.</description></item><item><title>Okta SSO sign-in issue impacting access to the DoiT console [resolved]</title><link>https://stspg.io/80nk2fl48xlg</link><guid isPermaLink="false">doit:2025-12-02T09:40:48.262Z</guid><pubDate>Tue, 02 Dec 2025 09:40:48 +0000</pubDate><description>We can confirm that service has been fully restored. Okta Single Sign-On (SSO) access to the DoiT Platform is now operating normally and sign-ins are completing as expected. 
Thank you for your patience and understanding while we worked to resolve this.</description></item><item><title>DoiT Console: Degraded availability due to third‑party CDN [resolved]</title><link>https://stspg.io/qw0mz7jjvktr</link><guid isPermaLink="false">doit:2025-11-18T12:51:52.343Z</guid><pubDate>Tue, 18 Nov 2025 12:51:52 +0000</pubDate><description>We can confirm that the issue with the third-party content delivery network has been fully resolved. Console access and performance have returned to normal. 
We appreciate your patience and understanding.</description></item><item><title>BigQuery Lens: Incorrect Storage Metrics [resolved]</title><link>https://stspg.io/tpz5g8z2mk28</link><guid isPermaLink="false">doit:2025-10-23T08:58:14.926Z</guid><pubDate>Thu, 23 Oct 2025 08:58:14 +0000</pubDate><description>The incident has been resolved and we are now seeing correct BigQuery Lens storage Metrics</description></item><item><title>investigating an increased level of 500 errors for customers [resolved]</title><link>https://stspg.io/wd652pbv7rqy</link><guid isPermaLink="false">doit:2025-10-23T05:06:24.000Z</guid><pubDate>Thu, 23 Oct 2025 05:06:24 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Email Delivery Disruption [resolved]</title><link>https://stspg.io/nj281s3yb6k3</link><guid isPermaLink="false">doit:2025-08-31T10:10:22.799Z</guid><pubDate>Sun, 31 Aug 2025 10:10:22 +0000</pubDate><description>The issue with our email service provider has been fully resolved. Email delivery is now operating normally across all features.</description></item></channel></rss>