Seattle, Washington
About the Lonnard James broadband newsroom
Lonnard James Broadband Review is an independent editorial publication covering U.S. broadband performance, spectrum policy, and internet infrastructure. It is based in Seattle and reports on the networks that connect households, the rules that govern them, and the tools people use to check whether their connection delivers what they pay for.
What we cover and why
The beat, explained
The beat sits at the intersection of measurement and regulation. Speed testing is how households experience their connection; spectrum policy and FCC rulemaking are how capacity and competition get decided years in advance. Reporting both together means a reader can connect a number on a screen to the auction or vote that shaped it.
That pairing is why the desk reads the procedural calendar as closely as it reads test results. A rulemaking can decide which frequencies carry a neighborhood's traffic, and a single speed test can show whether the promise made at the point of sale holds up on a Tuesday night. We treat both as parts of one story, not two separate feeds.
Independence and funding
No service to sell, no provider ranking for commission
The publication does not sell internet service and does not rank providers for commission. Any commercial relationship is disclosed, and editorial decisions are made without reference to it. The editorial standards page sets out the full policy, including how corrections are handled.
Read the full standards policyHow the reporting gets done
Stories come from filings, official statements, published research, and interviews. We read the procedural calendar. When the NTIA says the 7 GHz study completes by December 2026, we note what that gates and what happens next. When the FCC schedules a vote, we explain what the vote changes and when it takes effect.
Where a number appears in a story, we try to show where it came from and under what conditions it was collected. A result measured over a crowded evening network is a different fact from one taken on an idle line at midday, and readers deserve to know which one they are looking at.
Sources we work from
- Rulemaking dockets, filings, and official statements, read in full rather than from summaries.
- Published research and measurement studies, with the method and sample noted.
- Direct interviews with engineers, policy staff, and people living with the connections we cover.
- Public data on auctions, licensing, and funding programs, tracked on the calendar that governs them.
Where the newsroom is
3003 13th Ave W, Seattle, WA, 98119-2021
Seattle is a working choice rather than a symbolic one: the region holds major cloud infrastructure, several subsea cable landings, and a dense cluster of companies affected by the same federal decisions we cover. Stories about undersea routing or satellite service frequently have a local dimension here before they become national ones.
It also keeps the desk close to the people who build and run the networks. When a cable landing or a cloud region changes how traffic reaches the Pacific Northwest, we can follow the paperwork and the practical effect in the same week rather than months apart.
Who this is for
Readers arrive from three directions. Some have a connection problem and want to understand a test result. Some follow telecom policy professionally. Others are journalists, researchers, or local officials looking for a consolidated view of what has moved. The sections page is built to route each of them quickly.
Households with a slow connection
Start with how-to-run-a-reliable-speed-test and reading-your-speed-results guides, then check whether the plan you pay for matches what the line actually carries at the hours you use it.
Policy and telecom professionals
Follow spectrum and policy coverage for filings, votes, and auction milestones, with the procedural calendar kept visible so you can see what gates what.
Journalists and local officials
Use the sections page for a consolidated view of what has moved recently across infrastructure, service, and regulation, with sources you can check independently.
The stories we led with this cycle
Recent coverage includes Vermont's VT Speed Check public testing tool, launched October 6, 2026; the FCC's October 29 votes on device-testing labs and direct-to-device spectrum; reported efforts by Google, Meta, and Microsoft to secure backup land routes around the Red Sea; and the FCC's approval of 15,000 Starlink Mobile satellites with a waiver easing satellite wireless service.
Editing and corrections
Every story carries the date it was published and the date it was last changed. When a figure is wrong, we correct it and note what changed, rather than quietly swapping the number.
How do you handle a correction request?
Send the story link, the passage in question, and any source that supports the change to JesseGonzalez@lonnardjames.com. We check against the underlying filing or study and publish a dated note when the correction is confirmed.
Do you run your own speed test?
No. We are not a testing service and we do not have a proprietary speed test, and we say so on the guides. What we offer is reporting and explanation, with the sources visible so a reader can check the work.
How quickly does a tip get read?
Tips are read during working hours, Monday to Friday, 9:00 AM to 6:00 PM. Time-sensitive filings and outage reports are triaged first. Sources who need confidentiality should say so in the first message.
What is this publication not?
We are not a testing service, a consumer advocacy group, or a provider comparison site. If you need a recommendation on which plan to buy from which company, that is a different kind of help than we provide.
Contacting the newsroom
Tips, corrections, and press inquiries go to the contacts below. Corrections are welcome and are handled under the standards published on this site. Sources who need confidentiality should say so in the first message.
Phone
+1 206 438 9529Office hours
Monday to Friday, 9:00 AM – 6:00 PM