Ingestion Monitoring Dashboard
Live record of alert database freshness and ingestion activity. Freshness is measured directly from the alert database. All timestamps are UTC.
Live Monitoring Status
Data last updated: Oct 20, 2026, 2:52 PM UTC
+1 alert added in the last 48 hours
Sources monitored
- CMS Coverage Database19d ago
- Federal Registertoday
- CMS Transmittals (100-04)3d ago
- OIG Fraud Alerts & Guidance136d ago
- FDA Drug Approvals3d ago
Internal Run LogCron execution telemetry · last 30 days
Tracks executions of the /api/ingest logger. Alert data is also ingested via the GitHub Actions scraper pipeline, which writes directly to the database and does not always produce a run-log entry.
| Date | New Alerts | Updated | Completed At | Status |
|---|---|---|---|---|
| Oct 20, 2026Today | 0 | 0 | Oct 20, 2026, 6:00 AM UTC | Success |
| Oct 19, 2026 | 0 | 0 | Oct 19, 2026, 6:00 AM UTC | Success |
| Oct 18, 2026 | 8 | 0 | Oct 18, 2026, 6:00 AM UTC | Success |
| Oct 17, 2026 | 4 | 0 | Oct 17, 2026, 6:00 AM UTC | Success |
| Oct 16, 2026 | 1 | 0 | Oct 16, 2026, 6:00 AM UTC | Success |
| Oct 15, 2026 | 5 | 0 | Oct 15, 2026, 6:00 AM UTC | Success |
| Oct 14, 2026 | 0 | 0 | Oct 14, 2026, 6:00 AM UTC | Success |
| Oct 13, 2026 | 0 | 0 | Oct 13, 2026, 6:00 AM UTC | Success |
| Oct 12, 2026 | 0 | 0 | Oct 12, 2026, 6:00 AM UTC | Success |
| Oct 11, 2026 | 7 | 0 | Oct 11, 2026, 6:00 AM UTC | Success |
| Oct 10, 2026 | 8 | 0 | Oct 10, 2026, 6:00 AM UTC | Success |
| Oct 9, 2026 | 6 | 0 | Oct 9, 2026, 6:00 AM UTC | Success |
| Oct 8, 2026 | 2 | 0 | Oct 8, 2026, 6:00 AM UTC | Success |
| Oct 7, 2026 | 4 | 0 | Oct 7, 2026, 6:00 AM UTC | Success |
| Oct 6, 2026 | 0 | 0 | Oct 6, 2026, 6:00 AM UTC | Success |
| Oct 5, 2026 | 0 | 0 | Oct 5, 2026, 6:00 AM UTC | Success |
| Oct 4, 2026 | 9 | 0 | Oct 4, 2026, 6:00 AM UTC | Success |
| Oct 3, 2026 | 14 | 0 | Oct 3, 2026, 6:00 AM UTC | Success |
| Oct 2, 2026 | 20 | 0 | Oct 2, 2026, 6:00 AM UTC | Success |
| Oct 1, 2026 | 14 | 0 | Oct 1, 2026, 6:00 AM UTC | Success |
| Sep 30, 2026 | 20 | 0 | Sep 30, 2026, 6:00 AM UTC | Success |
| Sep 29, 2026 | 0 | 0 | Sep 29, 2026, 6:00 AM UTC | Success |
| Sep 28, 2026 | 0 | 0 | Sep 28, 2026, 6:00 AM UTC | Success |
| Sep 27, 2026 | 0 | 0 | Sep 27, 2026, 6:00 AM UTC | Success |
| Sep 26, 2026 | 5 | 0 | Sep 26, 2026, 6:00 AM UTC | Success |
| Sep 25, 2026 | 5 | 0 | Sep 25, 2026, 6:00 AM UTC | Success |
| Sep 24, 2026 | 10 | 0 | Sep 24, 2026, 6:00 AM UTC | Success |
| Sep 23, 2026 | 1 | 0 | Sep 23, 2026, 6:00 AM UTC | Success |
| Sep 22, 2026 | 0 | 0 | Sep 22, 2026, 6:00 AM UTC | Success |
| Sep 21, 2026 | 0 | 0 | Sep 21, 2026, 6:00 AM UTC | Success |
| Sep 20, 2026 | 4 | 0 | Sep 20, 2026, 6:00 AM UTC | Success |
Alert Database Coverage
- Total alerts monitored
- 2,159
- Specialties covered
- 33
- MAC jurisdictions
- 16
- Data refresh cadence
- Daily
last item Oct 1, 2026
last item Oct 20, 2026
last item Oct 17, 2026
last item Jun 5, 2026
last item Oct 17, 2026
Each lane shows the date its most recent item landed — counted from the alerts themselves, not from a job log. A long gap does not necessarily mean a lane is broken: some sources (OIG fraud alerts especially) publish rarely, and a check that finds nothing new writes nothing. We show you the date and let you judge, rather than a status light that can only ever say “fine.”
Workers’ Compensation coverage
State WC fee-schedule rates, derived from each state’s published schedule and verified against the CMS Physician Fee Schedule tool and the state’s Medicare contractor. A jurisdiction appears here only once its rates are loaded and its canary set passes — the full coverage plan lives on /workers-comp.
- Jurisdictions live
- 35
- Priced codes
- 17,300+
- Fee-schedule year
- 2026
Publication-to-Ingestion Speed
Days between the date printed on a government document and the day it entered CLV — measured across all 224 alerts published and ingested since Jun 5, 2026. Our one-off launch backfill of older policy is excluded: it measures archive depth, not speed.
How often we check
Every business day
We check every source every business day. How quickly a change reaches you after that depends on when its source system publishes it — and those systems differ, so we measure each one separately below rather than quoting a single average.
Median lag by source, since Jun 5, 2026
- CMS Coverage Database146 alerts
- 8 days
- Federal Register78 alerts
- same day
The Federal Register publishes to its public API the same day it publishes, so we carry those changes same-day. CMS posts Local Coverage Determinations to the Medicare Coverage Database several days after the date printed on the document, so the gap you see on that lane is CMS's publishing latency, not a delay in our monitoring — the same daily run that returns a same-day Federal Register notice returns a CMS document already several days old.
- Median lag
- 6 days
- Same day
- 34%
- Within 7 days
- 64%
- Fastest on record
- 0 days
Half of all 224 alerts arrived faster than this
77 of 224 arrived the day they published
143 of 224 within one week of publication
Same-day ingestion achieved
Fastest ingestion on record
Federal Register Proposed Rule: Medicare Program; Implementation of Sections 6219, 6220, and 6224 of the Consolidated Appropriations Act, 2026
CMS published: 2026-10-20 · CLV ingested: 2026-10-20 · Lag: same day
Methodology & Disclosures
- Alerts are ingested from government sources daily via an automated scraper pipeline. The “data last updated” timestamp reflects the most recent alert record written to the database, based on
created_at. - “New alerts” counts reflect documents newly added to the CLV database. Not all government publications result in new CLV alerts; documents outside CLV coverage scope are excluded.
- All alert records link to original government source documents. CLV Intelligence is not affiliated with or endorsed by CMS, the Federal Register, OIG, or FDA.
- This page refreshes on every request. The “data last updated” timestamp is derived directly from the alert database, not from the internal cron run log.