Network Reports
Live data pulled from Acadiana Mesh. Updates every time you load this page.
Additional reports: → Clock Sync Report
No Location Set
Action RecommendedThese repeaters have not configured a location (GPS coordinates are 0,0 or missing). Operators don't need to set a precise GPS coordinate — a general nearby area is enough. A location helps other operators understand network coverage and lets the community identify gaps.
| Repeater Name | Public Key Prefix | First Seen | Last Seen | Adverts (lifetime) |
|---|
Not on Firmware 1.14+
Action ImportantThese repeaters were observed sending only 1-byte path hash adverts and were not observed forwarding any multi-byte packets. This likely means they are running firmware older than 1.14 and will silently drop 2-byte and 3-byte packets. Once the switch to 2-byte and 3-byte packets on Companion nodes is made, these repeaters will no longer forward traffic to help the mesh.
Operators should update to firmware 1.14 or later. Flash your device →
path.hash.mode left at the default of 0. They simply weren't observed forwarding a multi-byte packet during the data window. Updating and setting path.hash.mode to 1 or 2 will help get you off this list. We also recommend that users periodically set their companion nodes to use 2-byte or 3-byte and send a message in the #test channel. This will generate multibyte traffic and allow us to see which repeaters are forwarding the traffic, indicating that they're updated and multibyte capable.
set path.hash.mode command on your repeater. The multibyte adverts only go out when triggered manually. This means a repeater on 1.14.0 may still appear on this list even if it's set to send out multibyte adverts. Upgrading to 1.14.1+ is recommended. However, 1.14.1 introduces a new issue where rxgain is disabled by default, which can reduce receive sensitivity. Re-enable it after upgrading with: set radio.rxgain on
▶ Click to view all repeaters not confirmed on firmware 1.14+
| Repeater Name | Public Key Prefix | Status | Last Seen | Adverts (lifetime) |
|---|
Clock Synchronization
Action RecommendedRepeater clocks that drift out of sync can cause packet deduplication failures, inaccurate network maps, and signature validation errors. We check clock health by comparing the timestamp embedded in each repeater's advert packet against the time the observer received it.
Recently Active Repeaters
Repeaters currently in the Acadiana area that have been recently heard by our observers, sorted by most recently active. Low-activity repeaters may not appear if they haven't been heard recently.
Note: If your repeater is not in this list it may simply be because an observer has not heard it, or it has not been active. Want to host an observer to help the mesh? Visit our Get Connected page.
| Repeater Name | Public Key Prefix | Firmware Status | Location | Last Seen | Adverts (lifetime) |
|---|