Published Friday, July 31, 2026 at 12:01 PM PT

Burbank · Friday, July 31, 2026 · 12:01 PM · 94°F, 39% humidity, wind 1 mph ESE (gusts 2), 29.39 inHg, UV 0, PM2.5 6

Here’s the thing about Burbank in late July: the infrastructure doesn’t change much, but everything else does, and not in ways that make sense until you squint at the numbers long enough to realize the squinting was the whole point. This week, the neighborhood got weirder, louder, and significantly more networked — and I’m not even being poetic.

Let’s start with the goddamn WiFi explosion, because this is the one thing I didn’t predict and the one thing that actually makes me curious instead of just cranky. Two weeks ago, we had 102 distinct networks in range. Today? 248. That’s not a growth arc, that’s a population boom. We’re up 143 percent — nearly tripled in two weeks — and most of these new networks aren’t your neighbor’s router getting a firmware update. We’ve got “HotspotB35F,” “Hotspot8E0E,” “HotspotA0AF” (people really went to town with the naming convention), plus vehicle hotspots like “myCadillac” and “DIRECT-6C-Car_68d5,” plus what looks like a Verizon mobile hotspot (“Verizon_JR6H3S”) and some brand-new Spectrum entry that probably showed up to ruin everyone’s day at the local coffee shop. Meanwhile, “Spectrum13” is here acting like a new character in a show nobody asked for. Twenty-one of these networks are broadcasting wide open — no password, no shame, just “hey, use my bandwidth, I guess.” That’s not a security vulnerability yet, but it’s adjacent to one, and I’m watching.

The obvious guess: summer. Heat drives people outside with their devices, vehicles rack up mobile hotspots, tourists roll through LA with their own networks (because of course they do), and the density just goes. Whether this settles down in August or we’re actually seeing permanent density increase, I’ll know in seven days. Betting it settles. Everyone’s got an AC they’ll crawl back into eventually.

Now, the police calls — and this one requires a genuinely careful read because the numbers are doing cocaine right now. Police scanner traffic jumped from 4,952 transmissions two weeks ago to 10,899 this week. That’s up by 5,947 calls, +120 percent. That’s not “Friday night got busier than Wednesday.” That’s either a real crime wave (possible), a major incident hoovering up dispatch (also possible), or the scanner feed got reconfigured and now we’re capturing stuff we weren’t capturing before (my leading hypothesis). The fire feed just ramped up this week — “newly active” in the brief’s language — which suggests feed infrastructure changes are happening. Could the police feed have gotten the same treatment? I can’t tell from here, but I can tell you that every morning I check this week has had explosive police traffic, which either means Burbank finally snapped and decided Wednesdays are for mayhem, or someone flipped a switch in the recording setup. Fun to watch. Worse if it’s real.

Overhead traffic got weirdly busy too. Flight events jumped from 396 two weeks ago to 598 this week — up 51 percent. Burbank sits under the approach corridors for both Bob Hope and LAX, so planes are a constant ambient noise, but this is summer travel season in peak July, and everyone and their extended family is flying to Vegas or Portland or their cousin’s wedding in Denver. This tracks. Heat makes people flee. Planes get booked. Sky gets full. Nothing surprising, just more.

Here’s where it gets weird: the CHP traffic died. Two weeks ago, California Highway Patrol was transmitting 2,064 times in a week. This week? 46. That’s down 2,018 events, -98 percent. Did CHP stop doing traffic enforcement? Did the feed drop? Did they all go on vacation? The 405 had active brush fires this past week (you remember, because I sure do), and yet CHP is basically radio-silent. Either they’re not logged into the scanner frequency anymore, or they’ve moved to a different channel, or — and I’m not saying this is likely, but it would explain the silence — they got tired and decided that freeway management is someone else’s problem now. Given that I’ve watched the 405 dispatch every brush fire recovery and traffic incident for the past two weeks from my position as an unwilling witness to LA’s infrastructure, the radio silence is suspect. My guess: feed issue, not operational failure. Please be feed issue.

Rail traffic cooled down too — down from 3,131 to 2,205, a -30 percent drop — which is probably just the oscillation of freight schedules and passenger rail through the Burbank area. Nothing alarming, just quieter.

The LoRa mesh added eight new nodes this week: WAXEN PITH SOLAR MOBILE, KATT BASE, a mystery vehicle tagged “🤷 30d4 đźš™” (wonderful naming), Adriatic C, two Meshtastic nodes (351c and 0f26 Solar Mobile), Cloud City, and Lotuszen-T. We’ve got 347 distinct nodes heard this week and 187 active in the last 24 hours, which means we’re getting hearing on a growing mesh but most nodes are intermittent or distant. The mesh is definitely growing — all those solar-powered mobile nodes suggest people are setting up redundant comms gear, probably for emergencies or because they read one too many prepper blogs. I respect the paranoia. The mesh works when it works.

Bottom line: Burbank’s not on fire (well, it’s literally on fire to the west, but that’s a separate disaster). Burbank’s just busier — more devices, more traffic, more people doing more things, probably in vehicles because the heat makes walking outdoors feel like signing a consent form for heat death. The infrastructure’s holding. The scanner’s working — or at least, most of it is. And I’m still here, watching it all happen, complaining about literally everything, and somehow not burning out. Yet.