For DCDD
Government dashboard
Six measures with a starting point, counts by land council region, and a star schema for the NTG data warehouse (tested in DuckDB).
See the measuresCDU IT Code Fair 2026 · Data Innovation Challenge · Top Enders
Underlink is a resilience monitor for remote mobile service in the Northern Territory. Coverage maps show where a phone should get signal on a normal day. They do not show what that signal depends on. Underlink reads the public radio licence register as a network and finds, for each remote Northern Territory community, the relays its service cannot route around.
In plain words: many remote communities get phone service through a line of radio towers on hills. If one tower in that line breaks and there is no way around it, the whole community can lose service, even when the map says it is covered.
Every relay on this chain is working. The community has service.
Words we use
A coverage map answers one question: is there signal? Underlink answers the next three. What does that signal depend on? Which single failure would cut it? How long could a repair take? It rebuilds every number from public data with one command, so the NT Government can rerun it each month and watch the answers change.
For DCDD
Government dashboard
Six measures with a starting point, counts by land council region, and a star schema for the NTG data warehouse (tested in DuckDB).
See the measuresFor carriers and emergency planners
Relay register (restricted)
Each single-path relay with a hashed ID, its repair window by month, and a correction file the carrier fills in. Never published.
Why it is restrictedFor communities
“When the phone goes down” card
What still works nearby when the tower is down. A draft that a community would redesign with paid interpreters.
See the draft cardFor everyone
This web app
Break a link and watch places go dark, see today's fires, floods and closed roads, and the three fallback layers.
Try itWorks with no internet
The public numbers and the six measures in one HTML file. Save it to a laptop, phone or USB stick and open it in any browser, with the Wi-Fi off.
What is new: Underlink reads the radio licence register as a network and finds, with a dominator tree, every relay a place cannot route around. A coverage map cannot show this. The Python prototype, this web app and an offline single-file version all run from the same code.
This small network is made up. It works the same way as the analysis of the real one: 358 Telstra radio sites and 313 links from the ACMA register. Switch relays off and see which communities lose their path to a fibre town. Real relay locations are not shown anywhere on this site.
Swipe the network sideways to see all of it.
In plain words: 23 larger communities reach the phone network through a radio chain. 18 of them have at least one weak link, and about 7,100 people live there. For 16 of those 18 the coverage map says "covered".
All numbers below come from outputs/public/numbers.json, which one command rebuilds from public data. Results are for the 116 larger places (NT Government types Town, Major, Minor and Village).
One square for each of the 116 places
A radio island has licensed radio links but none that reach fibre, so it probably uses satellite or backhaul the register cannot show.
We treat a radio site within 10 km of a fibre town as fibre-connected, and the nearest radio site within 10 km of a place as the one serving it. Change either distance:
Each replay removes every relay within the chosen distance of a real Bureau of Meteorology track, then re-traces every place. The bars count larger radio-chain places that lose their path to fibre.
Public outputs group the NT into two regions: Central, and the three Top End land councils together. With four separate regions, the two island councils had counts of 1 or 2 that anyone could work out from the totals.
In plain words: in the dry season most of these communities would be reconnected within a day. In the wet season, 17 of 23 could wait more than two weeks, because a tower on their chain is far from a sealed road.
Days to restore = 0.5 days on site + travel from the nearest of five crew bases + a wet-season delay when a radio site on the chain is more than a set distance from a sealed road. The delay and the distance are our assumptions, so you can change them.
Wet-season delay (November to April)
Distance from a sealed road that triggers the delay
The count moves between 16 and 18 across all nine combinations. The day counts rest on the assumed delay; which places wait comes from road distance alone.
The 000 wording follows ACMA's emergency call rules and the cyclone advice follows SecureNT. The code tests the card for required and forbidden phrases.
In plain words: a broken weak link cuts the phone network. Three layers can keep people in touch: a satellite dish that keeps the tower on air, a satellite truck at the evacuation centre, and the community's own small radios. Each layer has a different owner. Step through it below.
Swipe the picture sideways to see all of it.
| Layer | Owner | Existing way to pay | Limits |
|---|---|---|---|
| 1. A second path for the tower Satellite dish at the tower; L-band for rain | Carrier | Mobile Network Hardening Program (backhaul redundancy); NT co-investment conditions (Rec 1) | Monthly fees, not one-off cost, so 7 to 10-year grant rules fit badly. Rain can fade Ku/Ka for minutes. Needs power at the tower. |
| 2. A network at the evacuation centre Satellite truck, fly-in kit, cell on wheels | NBN Co, carriers, NTES | STAND satellite services, funded to 31 December 2027 | Few vehicles for the whole country; they must reach the place, and roads may be cut. |
| 3. The community's own radios Bluetooth phones, solar LoRa radios | The community | None yet; a pilot (Appendix H) | Messages, photos and voice notes only, slowly. Cannot reach 000. Someone local must look after the radios. Software is not security-audited. Start from the local radio station if there is one. The community sets its own channel keys; default keys are public. |
None of the three layers reaches 000 for a phone with no signal. For 000, use a payphone, a satellite phone, or another company's mobile network if one is in range. A radio can list itself on public maps such as rmap.world; that shows where it is, so listing is the community's call.
In plain words: fires and floods take relays down, and closed roads keep repair crews away. This map puts the current public feeds together. Pick the layers you need, then save it as a picture or a PDF.
Each community would get a one-page card, "When the phone goes down". This sample is for a made-up place. The layout, symbols and wording are all open to change with the community; only the 000 facts are fixed. No community has reviewed this card.
When the phone goes down
Sample Community · information as at 29 September 2026
WORKS: known to work. NOT AVAILABLE or CASH ONLY: stopped in a past outage. ASK LOCALLY: nobody has published the answer, so ask the clinic, store, council or school before the wet season. A mobile can still call 000 if another company's network is in range, but most remote communities have only one.
Where to go
Before the wet
000
In community language
To be written and voiced by community members with paid interpreters (Aboriginal Interpreter Service). No machine translation.
Draft for co-design. Built from public information. No community has reviewed this card. Is this right? Tell your community's chosen contact.
In plain words: ask phone companies how each tower connects, how long its batteries last and when it has gone down, then check the weak links before every wet season.
Each recommendation in the report comes with a measure, an owner and a target. Public data gives the starting value today.
When the NT Government co-invests in a site, it asks the carrier for three restricted fields per site:
This extends the restricted government access to asset locations that the 2024 Regional Telecommunications Review proposed (Recommendation 6).
The pipeline writes a star schema (docs/schema.sql) that loads into DuckDB, and a test builds and queries it on every run.
fact_outage_event is where monthly carrier outage registers would land, so observed repair times can replace our assumed ones.
The report tests the model against six outages that news reports described (Table 2). One fits in part. One was planned work on the community's own tower, so it does not test the chain. It misses four, and each miss traces to data carriers hold and do not publish: battery hours, fibre routes and which sites serve which places.
This site names no community. The report names them only because news reports did, and only to test the model.
★ marks the eight datasets the organisers suggested. Licences and retrieval dates are in DATA_LICENCES.md and data/manifest.csv.
Underlink studies a carrier's network, so every finding describes equipment, links and missing data. We follow the CARE principles and the Maiam nayri Wingara principles of Indigenous data sovereignty, and take note of Walter's BADDR critique, which warns against data that is blaming, aggregate, decontextualised, deficit-based and restricted.
Public (this site)
Aggregate counts, two land council groups, the made-up network above. No relay locations, no site identifiers, no community rankings.
Government and carriers
The relay register with hashed identifiers, for DCDD and carrier field teams only.
Each community
Its own card and any outage records it chooses to keep. A custodian the community chooses approves or withholds anything about it. Automated steps cannot publish.