Washington State Mesh Networks

Meshtastic and similar off-grid / amateur-radio data networks

Last updated: February 6, 2026 • Print: US Letter, 1" margins

Scope and definitions

This report focuses on mesh or mesh-adjacent radio data networks that are actively used or organized in Washington State, with an emphasis on Meshtastic (LoRa mesh texting/telemetry) and comparable systems.

LoRa mesh (store-and-forward): low bitrate, long range, battery-friendly. Examples: Meshtastic, MeshCore.
Ham IP “mesh/backbone” (microwave): high throughput point-to-point/point-to-multipoint networks for IP services. Examples: AREDN, HamWAN (PSDR).
LoRaWAN community LPWAN: not a mesh (star-of-stars), but similar hardware and use-cases for IoT telemetry. Example: The Things Network (Seattle community).
Commercial proprietary mesh: typically ad-hoc peer-to-peer (no public infrastructure). Example: goTenna (used by teams with shared equipment keys).

Completeness: LoRa meshes (Meshtastic/MeshCore) are often informal; there is no authoritative registry of “all networks.” This report lists networks and communities with public documentation and discovery tools.

Networks documented in Washington

Puget Mesh (Puget Sound region): Meshtastic

Community Meshtastic deployment around the Puget Sound area with published node builds and coverage maps, plus an organized weekly on-air “net.”

Weekly Meshtastic net: Mondays at 18:13:45 (6:13:45 pm). Uses the LongFast preset on slot 20 (US).
Discovery: Puget Mesh publishes equipment pages and coverage maps; not all nodes share position data.
Resources: Website + Meshtastic landing page + equipment pages.

https://pugetmesh.org/
https://pugetmesh.org/meshtastic/
https://pugetmesh.org/meshtastic/equipment/

Puget Mesh: MeshCore

Puget Mesh also tracks and maps MeshCore nodes. MeshCore is a newer LoRa mesh routing stack (MIT-licensed core), and the Puget Mesh site embeds a public node map; note that some nodes do not share location data.

https://pugetmesh.org/meshcore/
https://meshcore.co.uk/map.html

Meshtastic MQTT “seen nodes” map (global, filter for WA)

If nodes are bridged to the official Meshtastic MQTT server, they can appear on near-live maps. This is useful for discovering activity in Washington, but it will not show private meshes, and it depends on whether nodes share telemetry to MQTT.

https://meshmap.net/
https://meshtastic.liamcottle.net/

HamWAN / Puget Sound Data Ring (PSDR)

HamWAN is a non-profit developing best practices for high-speed amateur-radio IP networks, and the Puget Sound Data Ring is the Washington-region reference implementation. They publish a live map and documentation of sites and services.

Type: Part 97 microwave IP backbone (not low-power LoRa).
Discovery: PSDR “live” map and site pages.

https://hamwan.org/
https://hamwan.org/Puget%20Sound%20Data%20Ring.html
https://hamwan.org/Puget%20Sound%20Data%20Ring/Services/Map.html

Northwest Mesh (Western Washington): AREDN-oriented ham networking

Northwest Mesh is a Western Washington effort to expand AREDN coverage and lists local groups, maps, and how to join. It links to a “Seattle AREDN Mesh Map” and other PNW AREDN map resources (e.g., Yakima).

https://nwmesh.w7aw.org/
https://www.arednmesh.org/content/aredn-world-map
https://worldmap.arednmesh.org/

The Things Network (Seattle community): LoRaWAN

The Things Network is a LoRaWAN community ecosystem. In Washington, the TTN Seattle community page documents an official community with gateways and contributors. LoRaWAN is not a mesh, but it is commonly used alongside LoRa meshes for sensor telemetry.

https://www.thethingsnetwork.org/community/seattle/
https://www.thethingsnetwork.org/docs/lorawan/

Open source vs proprietary elements

System	Open source components	Closed / proprietary components	Notes (WA relevance)
Meshtastic	Firmware (GPLv3), Android app (GPLv3), iOS app, CLI/libs (various repos), documentation.	Radio silicon (Semtech LoRa transceivers), MCU SDKs/bootloaders; optional cloud services (MQTT brokers, app stores).	Strong WA presence via Puget Mesh + public MQTT maps.
MeshCore	Core routing code (MIT). Community/open tooling exists.	Depending on client choice: some official mobile clients are reported closed-source; radio silicon remains proprietary.	Puget Mesh maintains a MeshCore page + map links.
AREDN	Firmware based on OpenWrt with additional packages/patches; docs; map ecosystem.	Vendor RF hardware (Ubiquiti/MikroTik/etc) uses vendor bootloaders and often vendor OS in “stock” form.	PNW AREDN groups documented via Northwest Mesh; nodes visible on AREDN world map.
HamWAN / PSDR	Published standards/design docs; network services provided by members; common IP routing protocols.	Typical deployments use MikroTik RouterOS (commercial licensed) and other vendor RF gear.	Major WA backbone network with live map + site documentation.
LoRaWAN / TTN	Community network resources; open-source device stacks exist; documentation.	The LoRaWAN spec is published by the LoRa Alliance; many gateways/servers are commercial; radio silicon proprietary.	TTN Seattle community page tracks local gateways (not mesh).
goTenna (commercial)	(Typically none for the radio stack; ecosystem is product-led.)	Firmware/apps are proprietary; encryption/key handling depends on vendor implementation.	Mentioned because it’s a common proprietary “off-grid text mesh” alternative used by teams.

In practice, “open source” in this space usually means “open firmware + open client apps,” but it does not remove dependency on proprietary RF chipsets.

Encryption and security

Meshtastic

Channel traffic: AES-256 in CTR mode with a distinct key per channel; packet headers are unencrypted so relays can forward.
Limitations: PSK + CTR does not provide authentication; anyone with the PSK can impersonate other users on that channel.
Direct messages (newer versions): public-key crypto is being integrated for DMs/admin messages (see Meshtastic docs & release notes).

https://meshtastic.org/docs/overview/encryption/
https://meshtastic.org/docs/about/overview/encryption/limitations/
https://meshtastic.org/docs/development/reference/encryption-technical/

HamWAN / AREDN (Part 97 ham RF)

Ham RF links are governed by FCC Part 97 rules. In general, messages encoded for the purpose of obscuring meaning are prohibited. This strongly constrains “encryption on the air.” Some groups use authentication/access controls at the application layer, or carry traffic over Internet tunnels off-RF; policies vary by network and operator.

https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/section-97.113

LoRaWAN (TTN)

LoRaWAN uses AES-128 keys at multiple layers (network and application session keys). This is separate from “mesh”; end devices typically talk to gateways (star topology) and security depends on correct key provisioning and implementation.

https://lora-alliance.org/about-lorawan-old/
https://lora-alliance.org/wp-content/uploads/2020/11/lorawan1.0.3.pdf

Commercial proprietary meshes (example: goTenna)

Proprietary systems often advertise strong encryption (e.g., AES-256), but the security outcome hinges on key management and protocol details. Public advisories have highlighted key-handling issues and missing integrity checks in some implementations.

https://www.cisa.gov/news-events/ics-advisories/icsa-24-270-04

Amateur Radio use (Part 97)

Regulatory split that matters: Part 15 vs Part 97

Meshtastic on 902–928 MHz (US915): can be operated under unlicensed Part 15 limits (encryption allowed), or by licensed amateurs under Part 97 (often higher power/antennas allowed, but encryption to obscure meaning is prohibited).
AREDN / HamWAN: typically Part 97-only (ham license required), and the “no obscuring” rule shapes how you secure services.

Operational best practices (ham and non-ham)

Threat model: assume anyone can receive RF; focus on minimizing sensitive content.
Identity: PSK channels without signatures allow impersonation; treat “who said it” as advisory unless your stack supports signing.
RF hygiene: for microwave links, line-of-sight and interference dominate; for LoRa, height and antenna efficiency dominate.
Interworking: gateways (MQTT, IP tunnels) extend reach but change privacy assumptions.

Hardware, typical prices, and sources

Prices are “street” prices at time of writing and fluctuate. Links below show the URLs directly.

Meshtastic / LoRa mesh nodes (handhelds, fixed nodes)

Device	Typical role	Highlights	Typical price (USD)	Sources
Heltec WiFi LoRa 32 V3 (US915)	Low-cost node / dev board	ESP32 + SX1262, OLED, USB; good starter node	$25–$30	https://store.rokland.com/products/heltec-wifi-lora-32v3
LILYGO T-Echo (915)	Handheld / field node	nRF52840, e-ink display, low power	$45–$65	https://lilygo.cc/products/t-echo-lilygo https://lilygo.cc/en-us/products/t-echo-meshtastic
LILYGO T-Beam Supreme (915)	Mobile tracker / base node	ESP32-S3 + GNSS; good for vehicle/asset tracking	$37–$51	https://lilygo.cc/en-us/products/t-beam-supreme-meshtastic
RAK WisBlock Meshtastic Starter Kit (US915)	Modular node (fixed/mobile)	RAK4631 + modular sensors; very common “serious node” platform	$25 (direct) – $35+	https://store.rakwireless.com/products/wisblock-meshtastic-starter-kit
Seeed SenseCAP Card Tracker T1000-E (Meshtastic)	Ultra-portable tracker	Credit-card form factor; IP65; good for personal tracking/telemetry	$39–$45	https://www.seeedstudio.com/SenseCAP-Card-Tracker-T1000-E-for-Meshtastic-p-5913.html
RAK WisMesh Pocket V2	Turnkey handheld	Integrated enclosure + antenna; OLED; GNSS	$89.97	https://store.rakwireless.com/products/wismesh-pocket

AREDN / HamWAN-style microwave IP links (typical gear)

Device	Common use	Typical price (USD)	Notes	Sources
Ubiquiti LiteBeam 5AC	PtP / client links	$65–$86	Directional 5 GHz airMAX; often used as affordable CPE	https://store.ui.com/collections/wireless/products/litebeam-5ac https://www.bestbuy.com/product/ubiquiti-networks-litebeam-ac-gen2-airmax-ac-cpe-with-dedicated-management-radio-lbe-5ac-gen2-us-white/J3GK38GTJK/sku/11534380
Ubiquiti NanoStation M2 / M5	PtMP CPE / short PtP	$80–$100	Legacy but common; availability varies	https://store.ui.com/us/en/products/nsm2 https://store.ui.com/us/en/products/nsm5
MikroTik SXTsq 5 ac	Compact PtP / CPE	$49–$81	5 GHz; many HamWAN-style builds use MikroTik gear	https://www.wifi-stock.com/details/mikrotik-outdoor-wireless-device-with-an-integrated-antennasxtsq-5-ac-rbsxtsqg-5acd.html
MikroTik hAP ac lite	Indoor router / client edge	$59–$64	Often used as a local router behind an outdoor radio	https://www.walmart.com/ip/Mikrotik-hap-ac-lite-tower-RB952Ui-5ac2nD-TC-US/880583502

Where to look for Washington-specific “how to join” details

Puget Mesh: Meshtastic and MeshCore pages (settings, equipment, coverage).
HamWAN / PSDR: live map + site pages.
Northwest Mesh: AREDN groups, maps, and Groups.io entry points.

Quick-start: joining a WA Meshtastic net

Pick a US915-capable device (examples above) and flash Meshtastic firmware.
Set the region to US915 and start with the LongFast preset (common community default).
For the Puget Mesh net specifically, set frequency slot 20 and join Mondays at 18:13:45.
Use local resources to confirm channel settings and whether the mesh bridges to MQTT (which affects visibility on public maps).

https://pugetmesh.org/meshtastic/

If you operate on amateur allocations under Part 97 (vs Part 15), verify whether encryption is permitted for your use and comply with ID rules.

References (URLs shown)

Generated for print-friendly use. If you need this expanded to “all known nodes in WA,” the best approach is to export KML/CSV from the AREDN map and to query/filter Meshtastic MQTT maps for Washington; those datasets change continuously.