DoIT incident

Delayed GCP cost and usage data updates since January 10, 2026

Minor Resolved View vendor source →

DoIT experienced a minor incident on January 13, 2026 affecting Cloud Cost Analytics and Dashboards and 1 more component, lasting 7d 1h. The incident has been resolved; the full update timeline is below.

Started
Jan 13, 2026, 12:26 PM UTC
Resolved
Jan 20, 2026, 01:54 PM UTC
Duration
7d 1h
Detected by Pingoru
Jan 13, 2026, 12:26 PM UTC

Affected components

Cloud Cost AnalyticsDashboardsAnomaly Detection

Update timeline

  1. investigating Jan 13, 2026, 12:26 PM UTC

    We are currently investigating an issue where Google Cloud Platform (GCP) cost and usage data in the DoiT Console have not been updated since approximately January 10, 2026. Recent GCP billing and usage data may be missing or delayed in dashboards, reports, and alerts. Our team is continuing to investigate and to validate this assessment while monitoring GCP for any related events. We will post the next update as soon as we have more information. We appreciate your patience in the meantime.

  2. identified Jan 13, 2026, 01:30 PM UTC

    We have identified the cause of the delay in Google Cloud Platform (GCP) cost and usage data. Our team is working closely 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.

  3. identified Jan 14, 2026, 11:53 AM UTC

    We have verified that the issue originates from a problem with data exports in Google Cloud Platform (GCP). At this time, GCP has not yet resolved the underlying problem, so recent GCP cost and usage data may continue to appear delayed or incomplete. We remain in active contact with Google and will provide a further update as soon as we observe material progress or receive a clear timeline from their side.

  4. identified Jan 15, 2026, 02:02 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Jan 16, 2026, 04:41 PM UTC

    We are continuing to monitor this incident, which is caused by an upstream issue in the Google Cloud Platform (GCP) Cloud Billing export pipeline. GCP has indicated it will likely take several more days to clear the backlog, with export pipelines expected to resume next week and data gradually catching up afterwards; these timelines are estimates and may change. Because this is a GCP‑managed issue, we cannot directly expedite recovery, but we are closely coordinating with the GCP team. We will provide another update as soon as we see meaningful progress or receive a firmer timeline from GCP.

  6. identified Jan 19, 2026, 12:16 PM UTC

    Google Cloud Platform (GCP) has taken remedial action and is processing the backlog of billing data. We expect the missing data to be backfilled over the next 24–48 hours, although these timelines are estimates and may change. DoiT is already ingesting all backfilled billing data as it becomes available, and some customers may already see previously missing or incomplete days starting to populate in Cloud Analytics while the backfill is still in progress. We appreciate your patience while we work to backfill the GCP data. We will provide another update as soon as the backfill completes or if timelines change.

  7. monitoring Jan 20, 2026, 10:27 AM UTC

    We are now seeing GCP billing data fully backfilled for affected customers. DoiT has successfully ingested the backlog, and Cloud Analytics reports should once again reflect up‑to‑date cost and usage information. We are continuing to monitor data freshness to ensure everything remains stable.

  8. resolved Jan 20, 2026, 01:54 PM UTC

    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.