Data health.

Prices being checked

3 of 13 audited prices matched the provider's page, week of 19 Oct; 8 could not be read.

A price that moves 30% or more, or would reach a top three, waits for a second reading at least 12 hours later and is checked against the provider's own page, and so is one that fails a check or that a reader reports. Meanwhile the plan shows its last confirmed price and leads no list. Today 3 differ from the provider's page.

How the pipeline protects the numbers

• Only fetched numbers. Adapters throw on anything unexpected; nothing is hand-typed.
• Sanity gate. A fetch whose plan count halves or whose median price moves more than 2.5× is rejected and the previous snapshot kept, so a half-broken scraper cannot publish garbage.
• A changed price waits. A move of 30% or more, or into a top three, shows once a second reading agrees.
• Alerts. A provider stale for 3+ days opens a rolling GitHub issue that closes itself when the fetch recovers.
• Price history. Every change is recorded; offer pages show the latest movement.
• Catalogs refresh too. Model facts and hardware prices are re-fetched weekly with the same gate-and-alert pattern, so the model and rent-vs-buy pages do not drift.

provider pages