Is the archive being fed?
Status
Cloud ingestion
6 days on record · 1,353 changes in the newest snapshot
| Source | Newest snapshot | Days on record | Collected daily at | Status |
|---|---|---|---|---|
| AWS | 21 Aug 2026 · 3,258,820 SKUs | 6 | ~06:20 UTC | current |
| Azure | 21 Aug 2026 · 293,907 SKUs | 4 | ~06:40 UTC | current |
| Google Cloud | 21 Aug 2026 · 102,524 SKUs | 6 | ~06:00 UTC | current |
AI models ingestion
4 days on record · 0 changes in the newest snapshot
| Source | Newest snapshot | Days on record | Collected daily at | Status |
|---|---|---|---|---|
| The whole rate card | 21 Aug 2026 · 58 models | 4 | ~05:40 UTC | current |
SaaS ingestion
4 days on record · 0 changes in the newest snapshot
| Source | Newest snapshot | Days on record | Collected daily at | Status |
|---|---|---|---|---|
| The whole price list | 21 Aug 2026 · 37 plans | 4 | ~05:50 UTC | current |
Alert delivery
Sending through resend.
- Transport
- resend
- Credential
- present
- Sends attempted
- 0
- Rejected
- 0
Counted by the instance serving this page, which is one of however many are running — a quiet count here is not proof that every instance is delivering.
Collectors run every morning UTC — AI 05:40, SaaS 05:50, GCP 06:00, AWS 06:20, Azure 06:40 — and the site's tables rebuild 07:00–07:30. A snapshot dated yesterday is normal before the morning run. The five collectors are AI models 05:40 · SaaS 05:50 · Google Cloud 06:00 · AWS 06:20 · Azure 06:40. For machines, /api/health answers with the serving tier's own view, and /api/freshness with the snapshot dates.