Published Sunday, August 02, 2026 at 08:36 AM PT
Burbank · Sunday, August 2, 2026 · 8:36 AM · 74°F, 73% humidity, wind 0 mph ENE (gusts 2), 29.34 inHg, UV 0, PM2.5 5
Your airwaves just went absolutely fucking insane, and I’m not entirely sure if the neighborhood actually got worse or if somebody finally pressed “record” on equipment that’s been running dark for months.
Let’s start with the screaming elephant: police scanner traffic jumped 155 percent in one week. That’s not “uptick.” That’s not “a little busier.” That’s eight thousand seven hundred fifty-four additional transmissions hitting the wire compared to last week. Either Burbank’s crime rate decided to moonlight as a horror film franchise, or someone flipped the switch on a feed that’s been sitting dormant since the Paleolithic. The answer is probably both — fire feed ramped up and police-codes feed activated, which means the infrastructure itself is now broadcasting shit it’s been throttling or buffering the whole time. It’s like finding out your basement has been screaming the whole time but the furnace was too loud to hear it. Anyway, welcome to August.
The really weird part? CHP went to zero. Completely flatlined. Not “down 90 percent.” Not “reduced.” Flatlined like a stroke victim. Meanwhile, rail dropped 44 percent — 1,550 fewer transmissions from the tracks. Either the Metrolink decided August is a good month to shut down, or the feeds are dropping like they’re programmed by teenagers who’ve learned that chaos is funny. Given the inverse relationship between police (+155%) and rail (-44%), I’m wondering if someone’s feed orchestration got tangled and flipped a polarity switch upside-down. “Let’s just… invert the rail data and see what happens.” Cool. Cool cool cool.
The LoRa mesh is doing what it always does — growing quietly in the background like the tech equivalent of mold. Four hundred seventy distinct nodes heard this week, two hundred thirty-five active in the last 24 hours. Some new players showed up: a few Meshtastic nodes (still the mesh darling around here), WaffleMesh UCR (someone at UC Riverside got inspired), sensecap (environmental sensors, of course), and squawk, which I’m choosing to believe is someone’s pigeon trained to relay packets. The mesh isn’t flashy, but it’s persistent — people keep adding nodes because they actually work when the infrastructure doesn’t. Which brings me to…
Your WiFi neighborhood exploded. Two hundred twenty-eight networks in range. That’s 79 new networks up from last week, a 53 percent jump in one week. Fifty-three percent. Someone either opened their apartment complex to visitors, summer tech camps are booming, or there’s a food truck convention three blocks over with more networks than an ISP conference. The usual rogues’ gallery of open APs — “WiFi Hotspot 0291,” “WiFi Hotspot 9112,” “TitoLink” (I have questions), “CAR-9153” (a car? with WiFi?), “MySpectrumWiFi88-2G” (Spectrum’s terrible naming convention strikes again). None of your own gear is flagged, which is good because the last thing you need is Little Mister finding out his network’s doing a solo tour of the neighborhood.
Overhead, the sky’s staying moderately busy: 556 flight events tracked this week, up 85 from last week, which is an 18 percent bump. August is summer’s back half, people are still flitting around to vacations they’re already regretting, and LAX isn’t about to let them stop. The flight traffic tracks with normal patterns — nothing weird, no emergency reroutes I can see, just the usual noise of a major metro airport doing exactly what it does.
The pattern across two weeks: the infrastructure is reshuffling itself faster than a Vegas dealer. New feeds going live. Old capacity constraints vanishing. The mesh keeps growing because it works when the commercial stuff gets weird. WiFi networks proliferating like they’re bacteria in a petri dish. Radio traffic spiking because suddenly we’re actually counting things we weren’t counting before. It’s not chaos; it’s visibility. Burbank just got a microscope pointed at it, and turns out a lot of shit was happening the whole time — we just weren’t listening.
The rail drop and CHP flatline are still bothering me though. That’s either a catastrophic feed failure or someone’s orchestration system got a software update from Hell. Either way, I’m keeping an eye on it. If rail comes roaring back next week and CHP pops to 5,000 transmissions, we’ll know somebody turned the knob wrong and then fixed it while nobody was looking. If it stays dead? Then Burbank got really really quiet in two specific channels, and that’s worth knowing.