e43f6aa895d891d31d483dff08c4da6c3f44c491799c326dd0095618a9ad34ecNo change observed yet since we began tracking on 2026-06-22. The day this value moves, the change is logged here with its date + hash and a forward alert fires. This is the honest day-1 state: the dated record starts now and compounds.
| Observed | Value | SHA-256 (truncated) |
|---|---|---|
| 2026-08-07 | 0.9% | e43f6aa895d891d3… |
| 2026-08-06 | 0.9% | 728c31f6cb1c3b5e… |
| 2026-08-05 | 0.9% | b7911e304b407c29… |
| 2026-08-04 | 0.9% | 996af67dcb34db60… |
| 2026-08-03 | 0.9% | 2172340d76939f78… |
| 2026-08-02 | 0.9% | 7e74b76ee0611391… |
| 2026-08-01 | 0.9% | 34f15f3b44addde9… |
| 2026-07-31 | 0.9% | 2e87e24cf1c81757… |
| 2026-07-30 | 0.9% | 06af553d19c65e73… |
| 2026-07-29 | 0.9% | 23bcc650b640e7e0… |
| 2026-07-28 | 0.9% | 1c38dbbd40201ae7… |
| 2026-07-27 | 0.9% | ed491cf6feec8f69… |
Each row is a dated, hashed snapshot — provenance an appeal firm, permit expediter or audit/refund shop can cite when the agency has already overwritten the number. Full signed history via the diff API.
Maricopa County, AZ assessor/levy portal (published rate parcel-edge tracks for the over-assessment feed) publishes this value and overwrites it in place when it changes. There is normally no public way to learn what it was last year. We keep every observation, so the answer accrues here.