Data latency
Data latency in the DoiT console depends on the source's update cadence and DoiT's import schedule.
Cloud platforms
| Platform | Provider data freshness | DoiT refresh cadence | End-to-end latency |
|---|---|---|---|
| Amazon Web Services | AWS updates Cost and Usage Reports (CUR) at least once a day. | Every 6–8 hours after AWS updates the CUR file | 24–72 hours. See AWS cost data latency in DoiT console. |
| Google Cloud | See Google Cloud's frequency of data loads. | Hourly | 24–72 hours |
| Microsoft Azure | Azure Cost Management exports are updated daily. | Hourly | Up to 24 hours |
Other integrations
When you first connect a platform, DoiT immediately runs an initial data sync. The sync usually completes within a few hours, depending on the volume of historical data the source exposes. The cadence below applies after the initial sync.
| Platform | DoiT refresh cadence | End-to-end latency |
|---|---|---|
| Anthropic | Every 6 hours (Anthropic engagement metrics are aggregated daily) | Within 24 hours |
| Anyscale | Daily | Within 48 hours |
| ClickHouse Cloud | Every 6 hours | Within 24–26 hours |
| Cloudflare | Daily | Within 48 hours |
| Confluent Cloud | Every 6 hours | Within 48 hours |
| Coralogix | Every 6 hours | Within 24–26 hours |
| Cursor | Every 6 hours | Within 24–26 hours |
| Elastic Cloud | Daily | Within 48 hours |
| Fastly | Daily | Within 48 hours |
| GitHub | Every 6 hours | Within 24–26 hours |
| Grafana Cloud | Daily | Within 48 hours |
| Linode | Daily | Within 48 hours |
| Nebius | Every 6 hours | Within 24–26 hours |
| New Relic | Daily | Within 48 hours |
| PlanetScale | Daily | Within 48 hours |
| Temporal Cloud | Every 6 hours | Within 24–26 hours |
| Twilio | Daily | Within 48 hours |
| Vercel | Every 6 hours | Within 24–26 hours |
DataHub
Data sent to DoiT through DataHub is available in the console within about 15 minutes of ingestion, regardless of the format.