01
Start with increases
Look for districts where the pending load grew most since the previous published snapshot.
See increasesSNAPSHOT MOVERS
Comparing the 26 April 2026 snapshot against 26 April 2026. Every row is citeable — both snapshots are published and archived.
INVESTIGATION PATH
Movers compare two published snapshots. Use them to choose what deserves closer inspection, then open the district evidence pages before citing the change.
01
Look for districts where the pending load grew most since the previous published snapshot.
See increases02
Put two high-movement districts side by side to separate scale, wait, clearance pace, and rank change.
Open comparison03
Open the district page to see whether the signal persists across history or appears only in one snapshot window.
Open top mover04
Use CSV and methodology links so the movement window and source date remain visible beside the number.
Open dataDistricts where the backlog grew most since the previous published snapshot.
| District | Rank | Cases waiting | Change | Cleared / 100 | Repeat signal |
|---|---|---|---|---|---|
| Gorakhpur | #7 | 3,15,729 | ▲ 1,556 worse | 18.6 | Flagged in 0 of the last 6 published snapshots. |
| Ghazipur | #29 | 1,59,437 | ▲ 322 worse | 43.9 | Flagged in 0 of the last 6 published snapshots. |
| Gautam Buddha Nagar | #1 | 9,71,586 | ▲ 308 worse | 29.6 | Flagged in 6 of the last 6 published snapshots. |
| Jalaun | #54 | 83,897 | ▲ 282 worse | 77.6 | Flagged in 0 of the last 6 published snapshots. |
| Santkabir Nagar | #53 | 86,225 | ▲ 244 worse | 89.9 | Flagged in 0 of the last 6 published snapshots. |
| Etah | #59 | 75,204 | ▲ 240 worse | 109.9 | Flagged in 0 of the last 6 published snapshots. |
| Lucknow | #3 | 4,77,105 | ▲ 239 worse | 104.8 | Flagged in 6 of the last 6 published snapshots. |
| Prayagraj | #5 | 3,43,359 | ▲ 238 worse | 98.8 | Flagged in 0 of the last 6 published snapshots. |
| Fatehpur | #38 | 1,18,215 | ▲ 215 worse | 136.7 | Flagged in 0 of the last 6 published snapshots. |
| Mathura | #28 | 1,61,136 | ▲ 213 worse | 93.9 | Flagged in 0 of the last 6 published snapshots. |
Districts where the backlog shrank most since the previous published snapshot.
| District | Rank | Cases waiting | Change | Cleared / 100 | Repeat signal |
|---|---|---|---|---|---|
| Kanpur Nagar | #4 | 4,62,823 | ▼ 1,899 better | 369.8 | Flagged in 0 of the last 6 published snapshots. |
| Varanasi | #8 | 2,79,007 | ▼ 1,199 better | 251.9 | Flagged in 0 of the last 6 published snapshots. |
| Ghaziabad | #6 | 3,42,424 | ▼ 323 better | 79.2 | Flagged in 0 of the last 6 published snapshots. |
| Pilibhit | #52 | 91,370 | ▼ 209 better | 101.7 | Flagged in 0 of the last 6 published snapshots. |
| Shamli at Kairana | #70 | 61,777 | ▼ 189 better | 116.8 | Flagged in 0 of the last 6 published snapshots. |
| Ambedkar Nagar | #48 | 1,00,428 | ▼ 104 better | 135.4 | Flagged in 0 of the last 6 published snapshots. |
| Barabanki | #31 | 1,55,887 | ▼ 10 better | 54.4 | Flagged in 0 of the last 6 published snapshots. |
| Hamirpur | #69 | 62,434 | ▼ 7 better | 70.5 | Flagged in 0 of the last 6 published snapshots. |
Districts whose Watch rank worsened most — the pressure signal moved them up the list relative to their peers.
| District | Rank (prev → now) | Rank change | Cases waiting | Repeat signal |
|---|---|---|---|---|
| Mirzapur | #46 → #47 | Worsened 1 place | 1,00,601 | Flagged in 0 of the last 6 published snapshots. |