Data for Chico Apps
Live data status
Every live feed, how old it is now against its freshness promise (SLA), and how much of the last 24 hours it kept that promise. All feeds are within their SLA.
Scheduler heartbeat 0 s ago · as of 05:50:49 UTC · also as JSON. Refreshes itself every 30 seconds.
| Feed | Age | SLA | 24 h |
| NWS weather alerts | 36 s | 5 min | 99.9% |
| CHP incidents (Chico dispatch log) | 1.2 min | 5 min | 99.8% |
| CAL FIRE incidents | 54 s | 5 min | 99.9% |
| Live map bundle (CHP map, quakes, alerts, creek gauge, air, fire perimeters) | 1.0 min | 5 min | 99.8% |
| PG&E outages | 3.1 min | 10 min | 100% |
| Wire bundle (PG&E, CAL FIRE, Oroville, Caltrans signs and closures, UV, Amtrak) | 3.1 min | 10 min | 100% |
| Air quality (AirNow, Butte County AQMD) | 1.0 min | 15 min | 100% |
| Caltrans signs and lane closures | 3.1 min | 15 min | 100% |
| USGS earthquakes (history) | 2.3 min | 15 min | 99.9% |
| Caltrans closures and chain controls (history) | 3.6 min | 15 min | 100% |
| Study readings (creek, air, buses, incidents, temperature) | 13.4 min | 45 min | 100% |
| Venue event calendars | 12.6 min | 60 min | 100% |
| Local news feeds | 15.4 min | 60 min | 100% |
| Lake Oroville (CDEC hourly) | 3.1 min | 60 min | 84.2% |
| Reservoir storage (CDEC) | 32.8 min | 60 min | 83.8% |
| Creek and river gauges (USGS, CDEC) | 5.9 min | 60 min | 100% |
| NWS forecast | 29.0 min | 60 min | 100% |
| Hourly open-data specs | 38.7 min | 120 min | 100% |
Is the guide right?
90.5% of the rows we could check matched their own source on 2026-10-26 (19 of 21; 9 more couldn’t be checked).
| Night | Right | Checked | Couldn’t check | Fixed | Queued |
| 2026-10-26 | 90.5% | 21 of 30 | 9 | 2 | 2 |
| 2026-10-25 | 95.7% | 23 of 30 | 7 | 0 | 1 |
| 2026-10-24 | 100% | 24 of 30 | 6 | 0 | 0 |
| 2026-10-23 | 96.2% | 26 of 30 | 4 | 1 | 1 |
| 2026-10-22 | 95.2% | 21 of 30 | 9 | 1 | 1 |
| 2026-10-21 | 91.7% | 24 of 30 | 6 | 1 | 2 |
| 2026-10-20 | 92% | 25 of 30 | 5 | 1 | 2 |
| 2026-10-19 | 100% | 23 of 30 | 7 | 0 | 0 |
| 2026-10-18 | 95.2% | 21 of 30 | 9 | 1 | 1 |
| 2026-10-17 | 96% | 25 of 30 | 5 | 1 | 1 |
How it is checked. Every night 30 rows are drawn at random (12 places, 12 upcoming events, 6 nonprofit needs) and each is re-read from its own source: the place’s own website or OpenStreetMap, the page the event came from, the nonprofit’s own page. A row is right only if that source still says what we say. Rows that can’t be checked (a page that needs JavaScript, a CAPTCHA, a site that asks crawlers to stay away) are listed, never counted as right. Fixed automatically only where a rule already exists (a need the org no longer lists comes off; a dead website is marked); the rest goes to a person. Running since 2026-10-17.
Do people come back?
Visitors per Chico day on chicoflow.com, and how many had been before. Counting began 2026-10-17.
| Day | Visitors | Returning | Back within a week | From the home-screen app |
| 2026-10-26 | 29 | 3 (10%) | 3 | 0 |
| 2026-10-25 | 31 | 3 (10%) | 3 | 0 |
| 2026-10-24 | 29 | 4 (14%) | 4 | 0 |
| 2026-10-23 | 53 | 5 (9%) | 5 | 0 |
| 2026-10-22 | 59 | 2 (3%) | 2 | 0 |
| 2026-10-21 | 50 | 4 (8%) | 4 | 0 |
| 2026-10-20 | 50 | 1 (2%) | 1 | 0 |
| 2026-10-19 | 27 | 1 (4%) | 1 | 0 |
| 2026-10-18 | 20 | 0 (0%) | 0 | 0 |
| 2026-10-17 | 18 | 0 (0%) | 0 | 0 |
How it is counted. No cookies, and nothing stored that identifies anyone. Your browser keeps one value on your own device: the date of your last visit. Once a day, on the first page you open, it tells the server only “new” or “returning”, how many days since last time, and whether it is running as the home-screen app. The server counts each browser once a day using a fingerprint of IP address + browser with a random daily key that is kept only in memory and thrown away at midnight, so yesterday’s visitors cannot be matched or identified. Only these daily totals are saved. Bots are not counted. Limits: a browser that blocks storage counts as new every day; one person on two devices is two visitors.