DoIT Outage History

DoIT is up right now

There were 5 DoIT outages since February 16, 2026 totaling 600h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.doit.com

Minor April 6, 2026

AWS missing data

Detected by Pingoru
Apr 06, 2026, 01:39 PM UTC
Resolved
Apr 10, 2026, 01:41 PM UTC
Duration
4d
Affected: Cloud Cost AnalyticsDashboardsAnomaly Detection
Timeline · 4 updates
  1. identified Apr 06, 2026, 01:39 PM UTC

    We have identified an issue affecting AWS customers regarding missing data

  2. monitoring Apr 07, 2026, 12:07 PM UTC

    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.

  3. monitoring Apr 08, 2026, 11:14 AM UTC

    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.

  4. resolved Apr 10, 2026, 01:41 PM UTC

    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.

Read the full incident report →

Minor March 27, 2026

Intermittent AWS ingestion issue affecting subset of DCI customers

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
  1. 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.

  2. 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.

  3. 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.

  4. 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 →

Minor March 6, 2026

GCP Data Delivery Delays for billing exports to BigQuery

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
  1. 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.

  2. 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.

  3. 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 →

Minor February 16, 2026

Inaccurate AWS Cost Data

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
  1. 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.

  2. monitoring Feb 16, 2026, 07:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Feb 16, 2026, 07:44 PM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Feb 28, 2026, 12:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 16, 2026

Delayed GCP data delivery of cost and usage since February 11, 2026

Detected by Pingoru
Feb 16, 2026, 08:31 AM UTC
Resolved
Feb 19, 2026, 07:31 AM UTC
Duration
2d 22h
Timeline · 3 updates
  1. 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.

  2. 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.

  3. resolved Feb 19, 2026, 07:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track DoIT downtime and outages?

Pingoru polls DoIT's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when DoIT reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track DoIT alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring DoIT for free

5 free monitors · No credit card required