Auditing the 95%: A Data-Driven Look at Amazon Sidewalk Before I Bet a SKU on It

The cellular module for the Phase 2 build is sitting in a warehouse in China for three weeks while it makes its way to my workbench. Which gives me time to test: Amazon Sidewalk — does it actually reach the places I'd want a pet tracker to reach?

Amazon's marketing line is "approximately 95% of the US population is covered" — a number Amazon updates roughly annually as the bridge count grows. That's the number that justifies betting an entire product SKU on the Sidewalk tier, the way Tile did, the way Pebblebee did. So before I commit, I'm going to count.

What follows is the audit. Bridge math, coverage math, AWS-side cost math. Then a tangent on the AWS IoT integration path my collar's uplinks will actually take — because waiting for hardware is a good time to teeth-cut on the cloud side.

The 95% claim, dissected

The headline number traces to Amazon's Sidewalk launch press materials and the coverage.sidewalk.amazon public map. The claim is "approximately 95% of the US population is within Sidewalk coverage" — measured by counting Sidewalk-enabled Amazon devices (Echo, Ring) and computing which households fall within their effective sub-GHz / BLE radius.

Two words matter in that sentence, and they're the ones the marketing doesn't unpack. The phrase "approximately 95% of the US population" turns on that last word: population.

It's a population number, not a geographic number. And it's an eligibility number, not a reliability number. Both of those distinctions are the difference between "this will work for my customers" and "this will sometimes work for some of my customers."

Let's count the bridges

Public estimates put the US Echo install base at ~95–110 million devices as of mid-2026, with Ring devices adding another 12–15 million. Tile, since the Life360 acquisition completed and Sidewalk integration shipped, contributes another estimated 25–35 million bridge-eligible devices. Round numbers, but they bracket the order of magnitude.

That's a lot of bridges. Divided by ~129 million US households, that's roughly one bridge per household on average. Translated to area:

• Dense urban (NYC, SF, Chicago): thousands of bridges per square mile
• Suburban (Atlanta sprawl, San Jose, Houston suburbs): dozens per square mile
• Exurban / small-town: single digits per square mile
• Rural (most of MT, WY, NV, AK): approaching zero

The aggregate number is huge. The distribution is what kills the marketing claim for any specific use case.

Population covered is not land covered

The US is ~3.8 million square miles. The US is also ~333 million people. Those two numbers don't track each other.

Here's the actual Amazon Sidewalk coverage map for North America, screenshot today from coverage.sidewalk.amazon:

~80% of Americans live in urban areas, which occupy ~3% of the land. The other 20% — roughly 67 million people — are scattered across the remaining 97% of the country. So when Amazon says "95% of the population is covered":

• ~315 million people are inside coverage
• ~18 million people are outside coverage
• The 18 million sit in the 3.7 million square miles of low-density geography

That difference matters because dogs don't read census data. A dog that lives in San Francisco but escapes during a camping trip to the Sierra has just walked out of 95% coverage into 0% coverage, in one weekend. A retriever owned by a couple in suburban Pennsylvania near a state forest crosses the coverage edge every time it chases a deer.

A pet tracker that's "covered" in your driveway but "uncovered" at the dog park three blocks away ships exactly zero units to anyone who cares about finding their dog.

What coverage actually means

Even within the 95% population, "covered" is a more generous word than the marketing implies. There are four ways a bridge can be in your neighborhood but not bridging your packets:

1. Powered off. Echo Dots get unplugged. Spare bedrooms get cleaned out. Estimated unplug rate is somewhere between 10–20% of installed devices at any given time. The coverage map doesn't deduct for this.

2. Sidewalk opted-out. Amazon shipped Sidewalk with default-on in 2021, and gave users an explicit opt-out toggle. Estimated opt-out rate is in the 15–25% range of US Sidewalk-eligible households (no official number; press coverage and forum sampling). The coverage map shows potential, not actual.

3. WiFi-dead / backhaul-dead. Sidewalk uses your home WiFi to forward packets to Amazon's cloud. If the Echo has lost WiFi (router rebooted, ISP outage, the kid changed the password), the radio still works locally but the packets go nowhere. The collar gets an ACK. The owner gets nothing.

4. RF-shadowed. Bridges behind metal kitchen cabinets, basement Echos behind brick, Ring cameras under a metal awning — all sit in the device count but contribute little real coverage.

Multiply: even within the 95% population number, the effective real-world coverage is meaningfully lower. A reasonable internal estimate for "your packet actually reaches Amazon's cloud from this point on the map" is probably 60–75% of the headline number — which puts the real US household-level reliability at something like 57–71% of households when accounting for all four failure modes.

That's still huge. It's still better than any other crowdsourced network in the US. But it's not 95%. And the marketing doesn't tell you which 30–40% you're in until you ship.

So why am I still betting on it?

Because the alternative is worse, and the math at scale still works out.

Cellular comparison

Cellular LTE-M / NB-IoT (the comparison tier) gives you 99%+ population coverage and ~30% land-area coverage in the US — both better than Sidewalk on every axis. So why not just ship cellular?

Sidewalk's value isn't best-in-class coverage. It's "good enough" coverage at zero recurring cost to the manufacturer, in a country where the customer base skews urban/suburban (which is where Sidewalk is strongest). For a $79 collar with no monthly subscription as the product pitch, Sidewalk hits a price point cellular literally cannot, while covering the segment of the population that's most likely to buy a $79 collar in the first place.

What I'd ship

In the three-SKU plan, Sidewalk is the middle SKU — the "rides Amazon's infrastructure, no subscription, works for urban/suburban customers" middle tier between the LoRa-mesh community SKU (lowest cost, geographic gaps) and the Cellular SKU (highest cost, universal coverage). That's a defensible product matrix. Sidewalk doesn't have to be 95% reliable to be the right answer for the right customer. It just has to be honest about which customer.

AWS-IoT data path

When the cellular module finally lands and I start running real Sidewalk tests in three weeks, the cloud-side plumbing has to already be in place. Here's the path a single position broadcast takes from the collar to "the owner's app shows a pin on the map":

The breakdown of what I need to set up before any uplinks fly:

1. AWS account + region. Pick us-east-1. AWS IoT Core for Sidewalk runs in us-east-1 and us-west-2; everywhere else and you're routing across regions for no reason.

2. Wireless Device Profile. Tells AWS what kind of device this is (Sidewalk-spec, US915 band, your manufacturer info). One profile, reusable across every device I ship.

3. Destination. The routing rule that says "uplinks from this profile go to this IoT Topic." Single destination per product line.

4. IAM Role. Lets IoT Wireless actually invoke whatever you've pointed the destination at. Annoying to debug if you skip it; the API silently swallows the failure.

5. IoT Topic Rule with a SQL filter. Routes the message to a Lambda function. SQL syntax looks like SELECT *, topic() as topic FROM 'iot/wireless/sidewalk/+/uplink'. The + is the wildcard for device ID.

6. Lambda. Reads the base64 payload, decodes the binary, extracts lat/lng/timestamp/SNR, writes to DynamoDB, fires an SNS notification if the dog is outside its geofence.

That's the minimum. Total AWS setup time, having done this once before: ~30 minutes. The first time you do it, ~3 hours, because every tutorial assumes you know the difference between an IoT rule (the SQL filter) and an IoT destination (the routing endpoint), and they're different things with similar names.

The cost math at pet-tracker scale

Cloud costs are what eventually decide whether your "no subscription" product story is actually sustainable, so let's count them too. AWS IoT Wireless billing is roughly:

• Per-device fee: $0.10/device/month (Sidewalk-registered)
• Per-message uplink: $0.0008 per message
• IoT Rules executions: $0.15 per million
• Lambda: ~$0.0000002 per ~10 ms invocation
• DynamoDB writes: ~$0.25 per million write capacity units

For a single pet collar at three reasonable ping rates:

The hybrid mode is the answer. Sleep at 15-minute intervals when the accelerometer says "the dog isn't moving." Spike to 1-minute intervals when the 6-axis IMU detects motion (running, escaping, chasing). Average somewhere in the $5–8/device/month range. That's competitive with cellular but with no SIM to manage and no carrier relationship.

And for the customer experience: ~1 km of urban coverage at 1-minute resolution when the dog is moving, dropping to ~15-minute resolution when the dog is asleep on the couch. The accelerometer earns its place in the BoM all over again.

What I'm going to verify when hardware arrives

The audit-driven hypothesis list, things I'll test on the Sidewalk Starter Kit in the next few weeks:

1. Does my house actually have a working Sidewalk bridge nearby? The coverage map says yes. The reality I'll measure by registering the dev kit and watching whether uplinks land.
2. What's the actual roundtrip latency, packet-to-Lambda? Marketing implies "near real-time." I bet it's actually 5–30 seconds, and bursty.
3. What's the daily packet loss rate? Single-device samples in dense urban can hit 5–10% over 24 hours. I'll find out for my specific location.
4. Does coverage actually exist on the dog-walk route? Static map says yes; walking the route with a counting device will say definitively.
5. What's the bridge-density gradient on a 5 km drive away from the house? Specifically, where does the link die?

Those are the five numbers that decide whether Sidewalk graduates from "interesting product tier" to "shippable product tier" in this build.

What's next

The cellular hardware lands in ~3 weeks. The AWS-side plumbing should be wired up before then. The Sidewalk Starter Kit lands in ~2 days and I can start running coverage tests immediately. Next post is the actual results, with numbers instead of estimates.

If you want to follow along: the bridge density in your own neighborhood is at coverage.sidewalk.amazon. Worth checking before you bet a SKU on the network.