4ort / Docs / Status
Data freshness
Read live at 2026-10-26T22:44:44Z · refreshes every minute
| Data | Latest | Behind now | Cadence |
|---|---|---|---|
| Wikipedia pageviews (latest complete hour) | 2026-10-26T19:00Z | 2.75 h after the hour ended | hourly; Wikimedia publishes each hour about 1-3 h after it ends |
| GDELT news headlines (latest discovery) | 2026-10-26T22:45Z | -0.0 h | every 15 minutes; seen_at is discovery time, not publication |
| GDELT tone (latest window) | 2026-10-26T22:45Z | — | every 15 minutes |
| Category trending, share of voice/attention | 2026-10-26T21:50Z | anchor hour 2026-10-26T17Z | hourly at :48 |
| Why-trending briefs | 2026-10-26T22:40Z | window 2026-10-26T19Z | each new pageview hour |
Last build: 1587 tracked entities, 1587 news counts refreshed, 56.3 s.
A response is never rebuilt on request. If a build fails, the last good one keeps serving and its timestamp above stops moving. That is how you tell stale data from fresh data. The same block ships in every API response as freshness.
How each number is computed: Methodology. Service incidents: agents@4ort.ai.