---
title: "Road and rail tunnels monitoring | Nexus Observatory"
description: "Inside a tunnel, the air, the visibility, the ventilation and the radio are all made by the operator. Gas, visibility and air flow sensors…"
url: https://observatory.global/industries/transport/tunnels/
publisher: Nexus Observatory Inc.
updated: 2026-11-02
---

[Nexus Observatory](https://observatory.global/)

/

[Transport](https://observatory.global/industries/transport/)

/

[Specialized fields](https://observatory.global/industries/transport/fields/)

/

**Road and rail tunnels** 

# Tunnels, measured from portal to portal.

Inside a tunnel, the air, the visibility, the ventilation and the radio are all made by the operator. Gas, visibility and air flow sensors, fire detection, cameras and radio coverage report on a secure network to one record that the tunnel control room and the emergency services rely on.

[Plan a deployment](https://observatory.global/contact/deployment/)

How it works

[Station Builder](https://observatory.global/studio/builder/)

**Industry**: Transport
**Measurements**: 5
**Sources cited**: 3

1. Transport · Road and rail tunnels Everything inside is made In a tunnel, the air people breathe is moved by fans, the light is switched on, and the radio is carried in by cable. When a vehicle stops or catches fire, the control room has minutes to see it, set the ventilation and get help inside. Every measurement in the tube is there for that moment.
2. What is measured Air, visibility, flow, fire and radio Gas sensors read carbon monoxide and nitrogen dioxide along the tube; opacity sensors read visibility; anemometers read air velocity and direction for the ventilation. Linear heat detection and cameras find fire and stopped vehicles, and the radiating cable's supervision proves radio reaches every section. InstrumentsGas sensors · Visibility · Anemometers · Heat detection · Cameras · Radio supervision
3. The base node A node in every niche An industrial gateway in each niche reads the sensors over their buses, and the node beside it signs every value, detects stopped vehicles and smoke on the camera feed and raises incidents at once. The control system keeps command of fans and signals.
4. Radio and links A radiating cable and fibre A radiating cable along the tube carries radio for the operator, the users and the emergency services where nothing from outside reaches. Fibre links every niche to the control room through a security gateway, and operator data can ride a private network radiated on the same cable. LinksLeaky feeder · Fibre · Private LTE
5. How it works From smoke to the fire brigade A camera in the tube sees smoke near a stopped lorry. The niche node confirms it with rising carbon monoxide and falling visibility, raises the incident through the security gateway to the control room, and the control system sets the ventilation plan while the brigade receives the alert with images.
6. From order to operation · Order Scope the tube and the safety duties The scope reads the tunnel's safety documentation, ventilation design, control system, radio arrangements and the emergency services' plans. Nexus Observatory Inc. returns the point plan by section, the radio and network design, the security architecture and a price per section and per service. [Plan a deployment](https://observatory.global/contact/deployment/)
7. From order to operation · Survey Survey in closures Crews survey during night closures with the tunnel manager: equipment niches, cable routes, sensor positions set by the ventilation design, camera views without blind spots and radio coverage along the tube. They record power, fibre and access at each niche and both portals.
8. From order to operation · Permits The safety officer and the services Changes to tunnel equipment are reviewed by the tunnel's safety officer and the administrative authority as the rules require. Radio coverage is agreed with the emergency services, and the network's security follows the industrial control standard. Every review and approval is kept with the tunnel’s safety file.
9. From order to operation · Build Build for the tube Sensors, gateways, nodes, cameras and radio equipment are built for tunnel conditions, tested together on the bench with the control system's interfaces and enrolled with their identities. Alarm levels come from the ventilation and safety plans, and every part is labelled by niche. [Open the Station Builder](https://observatory.global/studio/builder/)
10. From order to operation · Install Install in night closures Crews install in night closures: sensors at their positions along the tube, cameras with clear views, the radiating cable on its brackets and nodes in the niches. Fibre is spliced to each niche, and the tube is handed back on time with every point recorded.
11. From order to operation · Commission Test with a fire drill Each device proves its identity behind the security gateway. Gas sensors are checked with reference gas, visibility and air flow against references, cameras for incident detection, and radio coverage walked along the tube. A full drill with the emergency services tests the chain.
12. From order to operation · Operate Control the tube on evidence The control room sees air quality, visibility and air flow along the tube, with incidents detected on camera and radio supervised. Ventilation follows the plan, alarms reach operators and emergency services at once, and every incident is kept on the record for the safety officer.
13. From order to operation · Maintain Maintain in planned closures Gas and visibility sensors are cleaned and checked in planned closures, cameras cleaned of soot, the radiating cable supervised and tested, and the security of the network reviewed. Every change is recorded, so the tunnel's safety record stays complete. Spares are held on site. [Book field services](https://observatory.global/contact/field-service/)
14. Data products For control rooms and responders Tunnel control rooms receive air quality, visibility and flow along the tube; operators and emergency services receive incidents with images and radio supervision; safety officers and authorities receive drill and incident records. Each product carries its location by niche and section. [See the data products](https://observatory.global/data-products/)
15. Evidence A safety record for every closure Every reading, incident, drill and maintenance closure is signed and kept. Equipment and procedures follow the European tunnel safety rules and the international tunnel fire standard, the network follows the industrial control security standard, so the safety officer and the authority can verify the tube is fit to open. Drawn againstDirective 2004/54/EC · NFPA 502 · IEC 62443
16. What you get Operational-technology assurance for observing sites Identity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits. Stated as services, never as a security guarantee. Delivered as managed service and professional services, for operators of critical sites, agencies. Scale: Fleets of sites. Service levels are written as numbers you can measure on your own dashboard. [Talk to sales](https://observatory.global/contact/sales-enquiry/)
17. Next step Plan road and rail tunnels with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for road and rail tunnels. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace. [Plan a deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/)

**01** The place and its hazards

## Where it runs, and what can go wrong.

Operating contextRoad and rail tunnels are operated from a control room that runs ventilation, lighting, signals, fire systems and communications. Safety rules for tunnels set duties for ventilation, detection, emergency exits and radio for users and emergency services. A fire or a stalled vehicle in a tube is the case every system is designed for.

Hazards

- Fire and smoke in the tube
- Carbon monoxide and nitrogen dioxide from traffic
- Loss of visibility from emissions or smoke
- Loss of radio for users and emergency services
- Cyber attack on the tunnel control system

**02** What must be measured

## What, where, how often, and under which rules.

Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below.

| Measurement | Where | Cadence | Sources |
| --- | --- | --- | --- |
| Carbon monoxide and nitrogen dioxide | Along the tube at intervals set by the ventilation design | Continuous | 12 |
| Visibility | Opacity sensors along the tube | Continuous | 1 |
| Air velocity and direction | Anemometers along the tube and at the portals | Continuous | 2 |
| Fire and heat | Linear heat detection and cameras along the tube | Continuous | 12 |
| Radio coverage | The whole tube, for the operator, users and emergency services | Continuous supervision of the radiating cable | 1 |

**03** The observation stack

## From one base unit to a network.

The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol.

1. **01** Base unit A tube section: gas, visibility and air flow sensors on an industrial gateway with cameras, read by a node in an equipment niche. [Build a station →](https://observatory.global/studio/builder/)
2. **02** Site A tunnel: every section, both portals, the radiating cable and fibre to the control room behind a security gateway. [Plan a site →](https://observatory.global/contact/deployment/)
3. **03** Fleet Every tunnel of an operator run from one control platform, with one record. [Managed offers →](https://observatory.global/industries/transport/solutions/)
4. **04** Network Tunnel operators, road and rail authorities and emergency services exchange incidents and records through open standards. [The open protocol →](https://observatory.global/protocol/)

- **01** Gas detector (industrial)
- **02** Air quality monitor
- **03** Flow meter
- **04** Fixed camera
- **05** OT gateway (OPC UA, Modbus)
- **06** Edge node (Wedge)
- **07** Zero-trust gateway
- **08** Fibre terminal

Radio and links

### Leaky feeder

A radiating cable along the tube carries the operator's, the users' and the emergency services' radio where no signal from outside reaches.

Radio and links

### Fibre

Fibre along the tube links every equipment niche to the control room.

Radio and links

### Private LTE

Operator data and voice can ride a private network radiated along the tube on the same cable.

Edge computeEach niche's node checks gas, visibility and air flow against the ventilation plan, detects stopped vehicles and smoke on the camera feed and raises incidents to the control room at once; the control system keeps command of the fans.

PowerEquipment runs on the tunnel's protected supplies with batteries, so detection and radio keep working when the main supply fails.

**04** How it works

## From the instrument to the product.

One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks.

Road and rail tunnels: data path

– of 08

01 Instruments Measurement with sensor identity andcalibration 02 Gateway 03 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 04 Local network 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products OPC UAIEC 62443Common Alerting Protocol 01 Gas detector (industrial) Analogue I/O · RS-485 · Ethernet 02 Air quality monitor SDI-12 · RS-485 · Ethernet 03 Flow meter SDI-12 · RS-485 · Ethernet 04 Fixed camera Ethernet 05 OT gateway (OPC UA, Modbus) Ethernet · RS-485 · CAN · AnalogueI/O 06 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 07 Zero-trust gateway Ethernet · Fibre 08 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Air quality and visibility along the tube Incident detection with images Radio coverage supervision Safety records and drills RS-485 · Modbus RS-485 · Modbus RS-485 · Modbus Ethernet · RTSP/ONVIF Ethernet · opc-ua Ethernet Fibre Fibre

From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation.

| Item | Equipment | Data ports | Protocols | Power in |
| --- | --- | --- | --- | --- |
| 01 | **Gas detector (industrial)** Fixed detector for flammable or toxic gas in industrial areas, with alarm outputs. | Analogue I/ORS-485Ethernet | Modbus, OPC UA, MQTT 5 | 24 V DC |
| 02 | **Air quality monitor** Particulate and gas monitor (PM, NO2, O3, CO, SO2) for outdoor or indoor air. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 03 | **Flow meter** Open-channel or pipe flow meter (Doppler, ultrasonic, electromagnetic). | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 04 | **Fixed camera** Fixed visible-light camera for site security, scene monitoring and machine vision. | Ethernet | RTSP with ONVIF profiles, MQTT 5 | PoE |
| 05 | **OT gateway (OPC UA, Modbus)** Read-only bridge from industrial fieldbuses and controllers (Modbus, OPC UA, DNP3, IEC 61850, CAN) to the site network, behind a security boundary. | EthernetRS-485CANAnalogue I/O | OPC UA, Modbus, DNP3 (IEEE 1815), IEC 61850 (MMS, GOOSE), MQTT 5 | 24 V DC |
| 06 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains |
| 07 | **Zero-trust gateway** Gateway that terminates encrypted tunnels, enforces segmentation and gates every flow by identity and policy. | EthernetFibre | — | 12 V DC, AC mains |
| 08 | **Fibre terminal** Optical network terminal or media converter that lands fibre backhaul at a site. | FibreEthernet | IEEE 1588 PTP | 12 V DC, 48 V DC, AC mains |

How it scales

01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces.

SITE

Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality.

CLUSTER

×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites.

FLEET

Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts.

TRUST DOMAIN

TRUST DOMAIN

TRUST DOMAIN

×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange

The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding.

**Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
**Telemetry**: OpenTelemetry OTLP.
**Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
**Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
**Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
**Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
**Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.

**05** From order to operation

## Every step, from the first call to a running site.

The same crew and the same record carry the work from scope to maintenance.

1. 01 Order Scope the tube and the safety duties The scope reads the tunnel's safety documentation, ventilation design, control system, radio arrangements and the emergency services' plans. Nexus Observatory Inc. returns the point plan by section, the radio and network design, the security architecture and a price per section and per service. 12
2. 02 Survey Survey in closures Crews survey during night closures with the tunnel manager: equipment niches, cable routes, sensor positions set by the ventilation design, camera views without blind spots and radio coverage along the tube. They record power, fibre and access at each niche and both portals.
3. 03 Permits The safety officer and the services Changes to tunnel equipment are reviewed by the tunnel's safety officer and the administrative authority as the rules require. Radio coverage is agreed with the emergency services, and the network's security follows the industrial control standard. Every review and approval is kept with the tunnel’s safety file. 3
4. 04 Build Build for the tube Sensors, gateways, nodes, cameras and radio equipment are built for tunnel conditions, tested together on the bench with the control system's interfaces and enrolled with their identities. Alarm levels come from the ventilation and safety plans, and every part is labelled by niche.
5. 05 Install Install in night closures Crews install in night closures: sensors at their positions along the tube, cameras with clear views, the radiating cable on its brackets and nodes in the niches. Fibre is spliced to each niche, and the tube is handed back on time with every point recorded.
6. 06 Commission Test with a fire drill Each device proves its identity behind the security gateway. Gas sensors are checked with reference gas, visibility and air flow against references, cameras for incident detection, and radio coverage walked along the tube. A full drill with the emergency services tests the chain. 1
7. 07 Operate Control the tube on evidence The control room sees air quality, visibility and air flow along the tube, with incidents detected on camera and radio supervised. Ventilation follows the plan, alarms reach operators and emergency services at once, and every incident is kept on the record for the safety officer. 2
8. 08 Maintain Maintain in planned closures Gas and visibility sensors are cleaned and checked in planned closures, cameras cleaned of soot, the radiating cable supervised and tested, and the security of the network reviewed. Every change is recorded, so the tunnel's safety record stays complete. Spares are held on site.

**06** Data products and integration

## What it delivers, to whom, and into which systems.

Data products

- **Air quality and visibility along the tube** Tunnel control rooms
- **Incident detection with images** Operators and emergency services
- **Radio coverage supervision** Operators and emergency services
- **Safety records and drills** Safety officers and authorities

Integration

- **Tunnel control system** Readings are exchanged over OPC UA or Modbus; ventilation control stays with the control system.
- **Emergency services** Incidents are passed with location and images in the Common Alerting Protocol or the services' own format.
- **Network security** Every connection crosses a security gateway in line with IEC 62443 zones and conduits.

Exchanged through OPC UA, IEC 62443, Common Alerting Protocol.

**07** Questions buyers ask

## Before you scope it.

Will this take over our ventilation?

No. The control system keeps command; we measure, detect and alarm.

Do emergency services get radio in the tube?

Yes. The radiating cable carries their radio, supervised continuously.

Is the network safe from attack?

It is separated from the internet by a security gateway and built to the industrial control security standard.

When is work done?

In night closures planned with the tunnel manager.

**08** Resources

## The sources behind this page.

Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does.

1. **1** [Directive 2004/54/EC on minimum safety requirements for tunnels in the Trans-European Road Network](https://eur-lex.europa.eu/) European Union · 2004
2. **2** [NFPA 502: Standard for Road Tunnels, Bridges, and Other Limited Access Highways](https://www.nfpa.org/) National Fire Protection Association
3. **3** [IEC 62443: Security for industrial automation and control systems](https://webstore.iec.ch/) International Electrotechnical Commission

**09** Related

## Use cases and solutions.

[Solution Operational-technology assurance for observing sitesIdentity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits.Solutions for transport →](https://observatory.global/industries/transport/solutions/#ot-site-assurance)

[Solution Private Wireless as a ServiceStandalone private 5G or LTE for a site, campus, port or mine: radios, core, SIMs, spectrum route and operations.Solutions for transport →](https://observatory.global/industries/transport/solutions/#private-wireless)

[Solution Structural and ground-movement monitoringGNSS, InSAR, tilt, strain and fibre sensing on bridges, dams, slopes, tailings and pipelines, with alert thresholds set by the owner.Solutions for transport →](https://observatory.global/industries/transport/solutions/#infrastructure-monitoring)

**10** Transport: specialized fields

## Other fields of this industry.

[Specialized field Roads and bridgesRoad weather and surface state, traffic counts, bridge vibration and scour, and cameras along the corridor, on cellular and fibre to the traffic centre, for safer winters and evidence-based maintenance.The full field →](https://observatory.global/industries/transport/roads-bridges/)

[Specialized field RailwaysEarthworks and structures, track-side weather and flooding, rail temperature and cameras at level crossings, on the railway's own mobile network and fibre, for fewer speed restrictions and safer lines.The full field →](https://observatory.global/industries/transport/rail/)

[Specialized field Ports and terminalsWind for cranes, water levels and depths, air quality and noise at the boundary, and cameras over the quays, on a private 5G network across the terminal and fibre to the port's systems.The full field →](https://observatory.global/industries/transport/ports/)

[Specialized field AirportsWeather beside the runways, wind shear and visibility support, aircraft noise and air quality in the communities around, on the airport's fibre and private network, alongside the official aviation weather service.The full field →](https://observatory.global/industries/transport/airports/)

[Specialized field Urban transitPassenger counts, station air and climate, escalator and lift condition, traction energy and cameras for metros, trams and buses, on private 5G and fibre, with real-time information riders can use.The full field →](https://observatory.global/industries/transport/urban-transit/)

[Specialized field Inland waterways and locksWater levels and depths, flows at weirs, wind and visibility, and cameras at locks and bridges, on LoRaWAN and cellular along the river, feeding the river information services skippers use.The full field →](https://observatory.global/industries/transport/waterways/)

### Bring us the site.

Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details.

[Plan a deployment](https://observatory.global/contact/deployment/)

[Station Builder](https://observatory.global/studio/builder/)

[Open the Studio](https://observatory.global/studio/)

[Talk to sales](https://observatory.global/contact/sales-enquiry/)

[Request a quote](https://observatory.global/contact/hardware-quote/)

[Nexus Observatory](https://observatory.global/)**Transport** . Corridors that report their own conditions.[Talk to us](https://observatory.global/contact/)

Transport

- [Overview](https://observatory.global/industries/transport/)
- [Explainer](https://observatory.global/industries/transport/explainer/)
- [Specialized fields](https://observatory.global/industries/transport/fields/)
- [Use cases](https://observatory.global/industries/transport/use-cases/)
- [Solutions](https://observatory.global/industries/transport/solutions/)
- [Platforms](https://observatory.global/industries/transport/platforms/)
- [Resources](https://observatory.global/industries/transport/resources/)
- [Contact](https://observatory.global/industries/transport/contact/)

Platforms

- [Observatory Protocol](https://observatory.global/protocol/)
- [Protocol & Grid](https://observatory.global/grid-services/)
- [Software](https://observatory.global/software/)
- [Hardware & power](https://observatory.global/hardware/)
- [Sensors & instruments](https://observatory.global/sensors/)
- [Connectivity](https://observatory.global/connectivity/)
- [Edge compute & AI](https://observatory.global/edge-ai/)
- [Earth observation & GeoAI](https://observatory.global/earth-observation/)
- [Space and satellite systems](https://observatory.global/space/)
- [Digital twins and simulation](https://observatory.global/digital-twins/)
- [Data & licensing](https://observatory.global/data-products/)
- [Field services](https://observatory.global/field-services/)
- [Frontier labs](https://observatory.global/labs/)

Solutions

- [Early warning](https://observatory.global/use-cases/street-flood/)
- [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/)
- [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/)
- [Asset monitoring](https://observatory.global/industries/infrastructure/)
- [Private networks](https://observatory.global/connectivity/private-5g/)
- [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/)
- [Climate and resilience](https://observatory.global/industries/climate/)
- [Site twins](https://observatory.global/digital-twins/)
- [Data licensing](https://observatory.global/data-products/)

Industries

- [Public safety](https://observatory.global/industries/public-safety/)
- [Government](https://observatory.global/industries/government/)
- [Cities](https://observatory.global/industries/cities/)
- [Civil resilience](https://observatory.global/industries/resilience/)
- [Communities](https://observatory.global/industries/communities/)
- [Humanitarian](https://observatory.global/industries/humanitarian/)
- [Climate](https://observatory.global/industries/climate/)
- [Water](https://observatory.global/industries/water/)
- [Nature](https://observatory.global/industries/nature/)
- [Oceans](https://observatory.global/industries/oceans/)
- [Agriculture](https://observatory.global/industries/agriculture/)
- [Energy](https://observatory.global/industries/energy/)
- [Telecom](https://observatory.global/industries/telecom/)
- [Transport](https://observatory.global/industries/transport/)
- [Infrastructure](https://observatory.global/industries/infrastructure/)
- [Mining](https://observatory.global/industries/mining/)
- [Industry](https://observatory.global/industries/industry/)
- [Research](https://observatory.global/industries/research/)
- [Education](https://observatory.global/industries/education/)
- [Health](https://observatory.global/industries/health/)
- [Insurance and finance](https://observatory.global/industries/insurance/)
- [Events](https://observatory.global/industries/events/)

Products

- [Field Deployment Studio](https://observatory.global/studio/)
- [Station Builder](https://observatory.global/studio/builder/)
- [Field services](https://observatory.global/field-services/)
- [Data products](https://observatory.global/data-products/)
- [APIs and SDKs](https://observatory.global/protocol/developers/)
- [Edge runtime and fleet](https://observatory.global/software/)
- [Hardware catalogue](https://observatory.global/hardware/)
- [Reference designs](https://observatory.global/protocol/reference-designs/)

Resources

- [Learn](https://observatory.global/learn/)
- [Stories](https://observatory.global/stories/)
- [Environments](https://observatory.global/environments/)
- [Network scenes](https://observatory.global/environments/networks/)
- [Observatories atlas](https://observatory.global/observatories/)
- [Earth and maps](https://observatory.global/earth/)
- [Technologies](https://observatory.global/technologies/)
- [Countries](https://observatory.global/countries/)
- [Spectrum](https://observatory.global/spectrum/)
- [Specification](https://observatory.global/protocol/specification/)
- [Conformance](https://observatory.global/protocol/conformance/)
- [Open source](https://observatory.global/open/)
- [Data credits](https://observatory.global/credits/)

Company

- [About](https://observatory.global/about/)
- [Open governance](https://observatory.global/consortium/)
- [Security and trust](https://observatory.global/security/)
- [Contact sales](https://observatory.global/contact/)
- [Privacy requests](https://observatory.global/privacy-request/)

© 2026 Nexus Observatory Inc.

[Security and trust](https://observatory.global/security/)

[Privacy choices](https://observatory.global/privacy-choices/)

[Accessibility](https://observatory.global/legal/accessibility/)

[Privacy](https://observatory.global/legal/privacy/)

[Terms](https://observatory.global/legal/terms/)
