- Detected by Pingoru
- May 08, 2026, 11:49 AM UTC
- Resolved
- May 13, 2026, 05:05 PM UTC
- Duration
- 5d 5h
Timeline · 3 updates
-
investigating May 08, 2026, 11:49 AM UTC
We have identified an AWS data ingestion issue in DoiT Cloud Intelligence impacting consolidated resold customers, we will provide an update shortly
-
monitoring May 10, 2026, 06:35 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 13, 2026, 05:05 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 12:02 PM UTC
- Resolved
- Mar 31, 2026, 04:21 PM UTC
- Duration
- 4d 4h
Affected: Cloud Cost AnalyticsDashboardsAnomaly Detection
Timeline · 4 updates
-
identified Mar 27, 2026, 12:02 PM UTC
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.
-
monitoring Mar 27, 2026, 04:09 PM UTC
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.
-
monitoring Mar 30, 2026, 02:53 AM UTC
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.
-
resolved Mar 31, 2026, 04:21 PM UTC
The AWS ingestion issue in DoiT Cloud Intelligence has been resolved, and the affected data has been updated. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 04:26 PM UTC
- Resolved
- Mar 09, 2026, 08:22 AM UTC
- Duration
- 2d 15h
Affected: Cloud Cost Analytics
Timeline · 3 updates
-
investigating Mar 06, 2026, 04:26 PM UTC
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.
-
investigating Mar 09, 2026, 12:46 AM UTC
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.
-
resolved Mar 09, 2026, 08:22 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 07:43 PM UTC
- Resolved
- Feb 28, 2026, 12:52 AM UTC
- Duration
- 11d 5h
Affected: Cloud Cost Analytics
Timeline · 4 updates
-
investigating Feb 16, 2026, 07:43 PM UTC
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.
-
monitoring Feb 16, 2026, 07:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
identified Feb 16, 2026, 07:44 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Feb 28, 2026, 12:52 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 08:31 AM UTC
- Resolved
- Feb 19, 2026, 07:31 AM UTC
- Duration
- 2d 22h
Timeline · 3 updates
-
identified Feb 16, 2026, 08:31 AM UTC
We have identified a delay in the delivery of Google Cloud Platform (GCP) cost and usage data. Our team is working with GCP to resolve the issue and is carefully monitoring data ingestion into the DoiT Console. At this time, recent GCP cost and usage data might seem delayed or incomplete. Our team is working diligently to restore normal reporting as soon as possible. We appreciate your patience in the meantime.
-
monitoring Feb 17, 2026, 08:49 AM UTC
GCP data delivery appears to be stabilizing. Our team is actively processing and backfilling the missing data into the DoiT platform. This process may take several hours to complete. We appreciate your patience.
-
resolved Feb 19, 2026, 07:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 12:26 PM UTC
- Resolved
- Jan 20, 2026, 01:54 PM UTC
- Duration
- 7d 1h
Affected: Cloud Cost AnalyticsDashboardsAnomaly Detection
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Jan 03, 2026, 12:02 AM UTC
- Resolved
- Jan 03, 2026, 07:35 AM UTC
- Duration
- 7h 32m
Affected: APIs
Timeline · 3 updates
-
investigating Jan 03, 2026, 12:02 AM UTC
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.
-
monitoring Jan 03, 2026, 01:19 AM UTC
The issue affecting some public API endpoints has been resolved. All impacted APIs are now operating normally. We will continue to monitor the system to ensure stability.
-
resolved Jan 03, 2026, 07:35 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 12:23 PM UTC
- Resolved
- Dec 11, 2025, 04:39 PM UTC
- Duration
- 4h 16m
Timeline · 3 updates
-
identified Dec 11, 2025, 12:23 PM UTC
Known issue: Magic link authentication is temporarily unavailable, fix in progress
-
monitoring Dec 11, 2025, 12:51 PM UTC
Magic link authentication is back online. Issue traced to third-party provider outage, continuing to monitor.
-
resolved Dec 11, 2025, 04:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 02:15 PM UTC
- Resolved
- Dec 10, 2025, 10:49 AM UTC
- Duration
- 1d 20h
Affected: Billing
Timeline · 4 updates
-
investigating Dec 08, 2025, 02:15 PM UTC
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.
-
identified Dec 08, 2025, 04:43 PM UTC
The issue with Billing Profiles has been identified and our team is working to implement a fix.
-
monitoring Dec 09, 2025, 08:43 AM UTC
A fix has been applied, and access to Billing Profiles in the DoiT console is recovering. We are monitoring for stability and will provide an update as soon as we confirm the issue is fully resolved.
-
resolved Dec 10, 2025, 10:49 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 09:40 AM UTC
- Resolved
- Dec 03, 2025, 05:29 AM UTC
- Duration
- 19h 48m
Affected: DoiT Console
Timeline · 4 updates
-
investigating Dec 02, 2025, 09:40 AM UTC
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.
-
identified Dec 02, 2025, 11:31 AM UTC
We’ve pinpointed the root cause behind failed Okta Single Sign-On (SSO) attempts to the DoiT console, which can present as a repeated redirect back to the sign in screen. A fix is currently being rolled out to restore access. During this process, some Okta SSO sign-ins may still be impacted. We’ll share the next update here once remediation is complete or if timelines change. Thank you for your patience.
-
monitoring Dec 02, 2025, 02:51 PM UTC
We are pleased to report that a fix has been implemented and we are actively monitoring the situation to ensure full resolution.
-
resolved Dec 03, 2025, 05:29 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:51 PM UTC
- Resolved
- Nov 19, 2025, 08:24 AM UTC
- Duration
- 19h 32m
Affected: DoiT Console
Timeline · 2 updates
-
investigating Nov 18, 2025, 12:51 PM UTC
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.
-
resolved Nov 19, 2025, 08:24 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2025, 08:58 AM UTC
- Resolved
- Nov 12, 2025, 03:37 PM UTC
- Duration
- 20d 6h
Affected: Cloud Cost AnalyticsDashboards
Timeline · 5 updates
-
investigating Oct 23, 2025, 08:58 AM UTC
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.
-
identified Oct 24, 2025, 11:18 AM UTC
We are pleased to update you that our team has identified the root cause causing misclassification and inflated storage metrics in BigQuery Lens. We appreciate your patience in the meantime.
-
identified Oct 25, 2025, 08:26 PM UTC
We are continuing to work on a fix for this issue.
-
identified Oct 30, 2025, 01:07 PM UTC
We are continuing to work on a fix to address the issue affecting storage metrics in BigQuery Lens. We expect to have a potential remediation shortly. Thank you for your patience as we work to resolve this issue.
-
resolved Nov 12, 2025, 03:37 PM UTC
The incident has been resolved and we are now seeing correct BigQuery Lens storage Metrics
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2025, 05:06 AM UTC
- Resolved
- Oct 23, 2025, 12:11 PM UTC
- Duration
- 7h 5m
Affected: Support & ConsultingCloud Cost AnalyticsFlexsaveDashboardsAnomaly DetectionDoiT ConsoleBilling
Timeline · 4 updates
-
investigating Oct 23, 2025, 05:06 AM UTC
We are continuing to investigate the issue. It appears the error originated from Cloudflare. You can track the status here: https://www.cloudflarestatus.com/
-
investigating Oct 23, 2025, 05:50 AM UTC
We are continuing to investigate this issue.
-
investigating Oct 23, 2025, 12:02 PM UTC
We are continuing to investigate this issue.
-
resolved Oct 23, 2025, 12:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2025, 10:10 AM UTC
- Resolved
- Aug 31, 2025, 03:05 PM UTC
- Duration
- 4h 55m
Affected: DoiT Console
Timeline · 2 updates
-
identified Aug 31, 2025, 10:10 AM UTC
We have identified an issue with our email service provider that is preventing emails from being sent. This may impact user invitations, alerts, budgets, cost anomaly notifications, and other email-based features. Our team is actively working to resolve the issue and will provide updates as they become available.
-
resolved Aug 31, 2025, 03:05 PM UTC
The issue with our email service provider has been fully resolved. Email delivery is now operating normally across all features.
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2025, 03:44 PM UTC
- Resolved
- Aug 07, 2025, 09:47 AM UTC
- Duration
- 3d 18h
Affected: Cloud Cost AnalyticsDashboardsAnomaly DetectionDoiT ConsoleBilling
Timeline · 5 updates
-
investigating Aug 03, 2025, 03:39 PM UTC
We are currently investigating a possible outage from Google resulting in missing Google Cloud billing data
-
identified Aug 03, 2025, 03:44 PM UTC
The issue is identified as a Google billing export to BQ. Google team is working on fixing the issue. Google incident: https://console.cloud.google.com/servicehealth/incidents?pageState=(%22psh_incidents_list_v2%22:(%22p%22:0,%22service%22:%5B%22Cloud%20Billing%22%5D))
-
identified Aug 05, 2025, 07:09 AM UTC
This is the latest update from Google Cloud team: "Our engineering team continues to address the data delays for the billing data exports to BigQuery. As a result of the mitigation implemented by the engineering team, the data delays continue to reduce in the billing exports to BigQuery. The system is now processing the data backlog and we are actively monitoring the progress of full recovery of billing data exports to BigQuery." Google incident: https://console.cloud.google.com/servicehealth/incidents?pageState=(%22psh_incidents_list_v2%22:(%22p%22:0,%22service%22:%5B%22Cloud%20Billing%22%5D))
-
monitoring Aug 06, 2025, 07:48 AM UTC
We are still seeing delays and missing data from the past few days. We are communicating with Google engineering team and this is handled with the highest priority. The Google incident is still open and you can follow it here: https://console.cloud.google.com/servicehealth/incidents?pageState=(%22psh_incidents_list_v2%22:(%22p%22:0,%22service%22:%5B%22Cloud%20Billing%22%5D))
-
resolved Aug 07, 2025, 09:47 AM UTC
The incident has been resolved and we are now seeing normal incoming billing data from GCP
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2025, 06:50 AM UTC
- Resolved
- Jul 17, 2025, 10:04 AM UTC
- Duration
- 3h 14m
Timeline · 3 updates
-
investigating Jul 17, 2025, 06:50 AM UTC
We're currently experiencing issues with the DCI console. Our technical team is actively investigating the problem. We'll provide an update as soon as we have more information. Thank you for your patience.
-
monitoring Jul 17, 2025, 07:39 AM UTC
The problem has been identified and resolved. The console is now accessible. Our team actively monitors the system to ensure stability and prevent further disruptions.
-
resolved Jul 17, 2025, 10:04 AM UTC
The issue affecting access to the DCI Console has been fully resolved. All services are now operating normally. We appreciate your patience and apologize for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Jul 04, 2025, 06:55 AM UTC
- Resolved
- Jul 04, 2025, 07:30 AM UTC
- Duration
- 34m
Affected: Support & Consulting
Timeline · 2 updates
-
identified Jul 04, 2025, 06:55 AM UTC
An issue has been identified with creating new requests on the DoiT platform. As a result, some users may experience issues or be unable to create new requests on the platform's "Expert inquiry" dashboard. Our engineering teams are currently addressing this issue and will share updates promptly as more information emerges.
-
resolved Jul 04, 2025, 07:30 AM UTC
We are happy to inform you that the issue has been fixed, and all affected customers can now submit new requests. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:33 PM UTC
- Resolved
- Jun 12, 2025, 06:57 PM UTC
- Duration
- 23m
Affected: Support & ConsultingCloud Cost AnalyticsAPIsDashboardsAnomaly DetectionDoiT ConsoleBilling
Timeline · 3 updates
-
investigating Jun 12, 2025, 06:33 PM UTC
We are currently experiencing disruption due to a global Google Cloud outage. As a result, some of our services — including access to and usage of the DoiT Console — may be intermittently affected. Our engineering teams are actively monitoring the situation and working closely with Google to track progress. We will provide timely updates as more information becomes available.
-
investigating Jun 12, 2025, 06:42 PM UTC
We are continuing to investigate this issue.
-
resolved Jun 12, 2025, 06:57 PM UTC
This incident has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2025, 09:01 AM UTC
- Resolved
- May 06, 2025, 09:35 AM UTC
- Duration
- 8d
Affected: Cloud Cost AnalyticsDashboards
Timeline · 3 updates
-
identified Apr 28, 2025, 09:01 AM UTC
We would like to inform you that GCP billing data for a subset of customers has been missing or incomplete since April 25, 2025. Our team has identified the root cause of the issue and is actively working on a resolution to restore full data integrity. We sincerely appreciate your understanding and patience as we work to resolve this matter as quickly as possible. We will provide further updates as progress is made.
-
monitoring Apr 29, 2025, 11:29 AM UTC
Google has completed the backfill operation, but currently, the refreshed data is not consistently visible across all customer accounts. Our ingestion pipelines are still finalising the processing of the latest update. We are closely monitoring the progress and expect the issue to be fully resolved soon.
-
resolved May 06, 2025, 09:35 AM UTC
We are pleased to inform you that the underlying issue with Google Cloud Platform (GCP) has been fully resolved. Following this, our engineering team has successfully completed the backfill of all affected GCP data to ensure data integrity and continuity. We appreciate your patience and understanding throughout the resolution process.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2025, 06:09 PM UTC
- Resolved
- Apr 14, 2025, 06:45 AM UTC
- Duration
- 4d 12h
Affected: Billing
Timeline · 2 updates
-
identified Apr 09, 2025, 06:09 PM UTC
Due to a problem in our billing pipeline, some invoices are missing AWS support totals. Engineers are working to update this, after which invoices for affected customers will be cancelled and re-issued.
-
resolved Apr 14, 2025, 06:45 AM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2025, 12:36 AM UTC
- Resolved
- Mar 18, 2025, 02:16 AM UTC
- Duration
- 1h 40m
Affected: DoiT Console
Timeline · 3 updates
-
investigating Mar 18, 2025, 12:36 AM UTC
We are aware of an SSO login issue to the DoiT console. Our engineers are investigating this problem.
-
investigating Mar 18, 2025, 12:36 AM UTC
We are continuing to investigate this issue.
-
resolved Mar 18, 2025, 02:16 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2025, 10:33 AM UTC
- Resolved
- Mar 03, 2025, 01:09 PM UTC
- Duration
- 10d 2h
Affected: Cloud Cost Analytics
Timeline · 3 updates
-
investigating Feb 21, 2025, 10:33 AM UTC
We are experiencing an issue with our daily and weekly digest email reports. Our engineering team is actively investigating the problem and working on a fix. We apologize for the inconvenience and will provide updates as soon as more information is available. Thank you for your patience.
-
monitoring Feb 24, 2025, 09:00 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 03, 2025, 01:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2025, 10:31 AM UTC
- Resolved
- Jan 28, 2025, 06:24 PM UTC
- Duration
- 6d 7h
Affected: Billing
Timeline · 3 updates
-
identified Jan 22, 2025, 10:31 AM UTC
We've found an issue with our billing and invoicing for a subset of GCP customers for December 2024. The issue has been identified, and the team is busy working on a fix. After the fix has been implemented, new invoices will be issued.
-
identified Jan 23, 2025, 12:30 PM UTC
We are currently in the final stages of resolving all the December 2024 billing cycle invoices. An update will be sent once all invoices are ready and available. Thank you for your patience.
-
resolved Jan 28, 2025, 06:24 PM UTC
The invoices for all affected GCP customers were generated and are being sent out today.
Read the full incident report →
- Detected by Pingoru
- Dec 25, 2024, 05:17 PM UTC
- Resolved
- Dec 28, 2024, 03:14 PM UTC
- Duration
- 2d 21h
Affected: Cloud Cost AnalyticsAPIsDashboardsAnomaly DetectionDoiT Console
Timeline · 3 updates
-
investigating Dec 25, 2024, 05:17 PM UTC
We are experiencing a delay of CloudHealth data, which is causing inaccuracies in the reporting tools for affected customers. Our engineering team is investigating the issue.
-
investigating Dec 25, 2024, 05:18 PM UTC
We are continuing to investigate this issue.
-
resolved Dec 28, 2024, 03:14 PM UTC
This incident has now been resolved and all data is up-to-date.
Read the full incident report →
- Detected by Pingoru
- Dec 23, 2024, 11:07 AM UTC
- Resolved
- Dec 24, 2024, 08:24 AM UTC
- Duration
- 21h 17m
Affected: DoiT ConsoleBilling
Timeline · 3 updates
-
investigating Dec 23, 2024, 11:07 AM UTC
Customers may experience and issue when creating or editing Billing Profiles & paying Invoices via the DoiT console. Our Engineering Team are actively investigating the cause of this issue and we will provide updates on our progress shortly.
-
monitoring Dec 23, 2024, 11:49 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 24, 2024, 08:24 AM UTC
We are happy to advise this issue has now been resolved. Thank you for your patience whilst we worked through the incident.
Read the full incident report →
