Update - We are continuing to work on a fix for this issue.
Jan 15, 2026 - 14:02 UTC
Update - 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.
Jan 14, 2026 - 11:53 UTC
Identified - 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.
Jan 13, 2026 - 13:30 UTC
Investigating - 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.
Jan 13, 2026 - 12:26 UTC
Resolved -
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.
Jan 3, 07:35 UTC
Monitoring -
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.
Jan 3, 01:19 UTC
Investigating -
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.
Jan 3, 00:02 UTC