Mesa code cases in 85209 that moved between our dated copies

What this page is71,274 rows held · newest sealed read 2026-08-29

• 13 cases in 85209 sat on two of our dated copies carrying a different status word. 16 more are in a copy and were not in the copy before it, and 3 were in a copy and gone from the next one.
• The moves we saw most in 85209: In Violation to Closed (11), Citation Issued to Closed (2).
• 11 of the 16 arrivals carry a Mesa opened date OLDER than the copy before they showed up, so Mesa had already opened those and they only reached our copy afterwards. 5 carry a date on or after it.
• We hold 71,274 sealed case rows for 85209 across 31 dated copies, 22 Jul 2026 to 29 Aug 2026. Mesa's own file moved 7 times in that stretch, so most of those copies are the same file read again.
• 2,306 85209 cases are in our newest copy. 62 of them carry a status other than Closed.

Real rows out of our sealed copies

These are rows we read out of dated copies we keep ourselves. The live source shows today only, so once a row moves, what it said before is gone from the place you would go to look.

Who published the data on this page

• Every code-compliance case on this page was opened and published by the City of Mesa, Arizona, not by us. We keep dated copies of the file the City puts out; the case numbers, the status words and the addresses inside those rows are theirs.
• The City asks anyone using this data to list the City as its source. So, plainly: this page uses material published by the City of Mesa, Arizona.

What this page cannot tell you

• Mesa republishes about once a week, so our dates are accurate to about a week. We read the file every day and hold 31 dated copies, but the file behind them only changed 7 times, on 22 Jul 2026, 26 Jul 2026, 30 Jul 2026, 6 Aug 2026, 13 Aug 2026, 20 Aug 2026, 27 Aug 2026. Every comparison on this page is between two copies that carry different Mesa update stamps, never between two reads of the same file.
• In our copy is not opened this week. A case counted as an arrival is one that is in a copy and was not in the copy before it. That is first seen by us. 11 of the 16 arrivals in 85209 carry a Mesa opened date older than the earlier copy.
• Out of the file is not closed. A case that leaves Mesa's file has left the file, and that is the whole of what we can tell you. It is not a closure, we do not know why a row goes, and across the city two cases that left came back in a later version.
• The status words are Mesa's own, and Mesa cuts them short. The field is 19 characters wide in the source, so the file itself carries “Voluntary Complianc”, “In Violation/Un-coo”, “Forced Compliance -”. We print them exactly as the copy sealed them and we do not tidy them up or translate them.
• No street address is printed on this page. Our sealed copies carry the address Mesa publishes for every case, and this page prints the case number and the ZIP instead. The case number is what Mesa’s own system looks a case up by, so a row here is one you can check against the city rather than one you have to take from us.
• Mesa's own download is free and carries most of this. It publishes the same cases with the date each one opened and the date it closed. What it does not carry is what a case said on a past day. That gap is the only thing these pages add, and if the free file is all you need, use the free file.
• 8 days between 22 Jul 2026 and 29 Aug 2026 have no sealed copy. Nothing was collected on those days. A change that happened and reversed inside one of those gaps is not on this page.
• This is Mesa's published file, not Mesa's whole record. We hold what the city put on its public download on the day we read it. A case the city never published is not here and we cannot tell you how many of those there are.

More from this feed

• Up one level: Mesa code-compliance changesThe whole feed, its price, and how the file arrives.
• What is and is not in this feedEvery source we read for it, how often, and the ones we refuse to collect.