--- title: "Radio observatories and quiet zones | Nexus Observatory" description: "Radio telescopes listen for signals far weaker than any phone. Every transmitter near the site, every faulty device and every satellite passing over can…" url: https://observatory.global/industries/research/radio-observatories/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Research](https://observatory.global/industries/research/) / [Specialized fields](https://observatory.global/industries/research/fields/) / **Radio observatories and quiet zones** # The sky, kept quiet enough to hear. Radio telescopes listen for signals far weaker than any phone. Every transmitter near the site, every faulty device and every satellite passing over can drown the sky. Interference monitoring across the quiet zone, with site weather and precise timing, tells astronomers what to trust and regulators what to find. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Research **Measurements**: 4 **Sources cited**: 3 1. Research · Radio observatories and quiet zones Signals fainter than any phone Radio telescopes listen for signals far weaker than any phone, so every transmitter near the site, faulty device or passing satellite can drown the sky. Quiet zones protect major observatories, and international criteria say how much interference is too much. Measuring it is how both are enforced. 2. What is measured The spectrum, the weather and time Wideband receivers at the array and around the quiet zone sweep the radio spectrum continuously. Weather stations measure the water vapour that limits high-frequency observing, and timing receivers keep the site clocks that interferometry depends on. Every instrument keeps its calibration and position with the site record. InstrumentsInterference monitors · Weather stations · Timing receivers 3. The base node Sky or transmitter The processing node compares each sweep with the protection criteria, flags events, estimates their direction and identifies known satellite passes. It tags every observation with the interference present, so astronomers know what in their data is the sky. Every value is signed at the node before it leaves. 4. Radio and links Nothing that transmits Inside the quiet zone nothing may transmit, so every monitor reaches the observatory over fibre. Mobile monitoring vans used to track sources report over cellular only from outside the zone boundary. When one path fails, the other carries the data. LinksFibre · Public cellular outside the zone 5. How it works From a spike to a silenced source A strong signal appears in a protected band every evening. Monitors at three points estimate its direction toward a farm inside the zone. The regulator visits and finds a faulty device; it is replaced, the band is clean again and the event is closed in the database. 6. From order to operation · Order Scope the zone and the bands The scope reads the observatory's bands, its quiet zone rules, past interference and the regulator's enforcement process. Nexus Observatory Inc. returns the monitor plan, processing design, interference database and a price per site and per year. The scope is agreed before any site work begins. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey the radio environment Crews survey the site and zone with a portable receiver: existing interference, candidate monitor sites with views across the zone, fibre routes and shielded rooms. Findings are recorded with spectra and directions. Findings shape the kit for each site before anything is built. 8. From order to operation · Permits Regulator and site rules The spectrum regulator agrees how monitoring supports enforcement in the quiet zone, the observatory approves every installation for its own emissions, and land owners approve remote monitors. Every approval is kept with the site record. No crew goes to site before its approvals are in place. 9. From order to operation · Build Build quiet Receivers, antennas and nodes are built and tested in a shielded chamber so they add no interference, calibrated across the bands, enrolled with their identities and run together before shipping. Nothing ships until the whole kit has passed its tests together. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install with fibre Crews mount monitor antennas, install receivers and nodes in shielded enclosures, lay or connect fibre and verify the installation adds nothing to the spectrum. Every monitor is photographed and recorded. Crews follow the site safety plan throughout the work. The site record is updated before the crew leaves. 11. From order to operation · Commission Commission against known sources Each node proves its identity and time. Known test signals and satellite passes are detected and located, sweeps are compared with a reference receiver, and interference tags are checked against observers' own data. Acceptance is recorded with the owner before handover. 12. From order to operation · Operate Tag and find interference Observers see the interference present during every observation; the observatory's spectrum manager sees events and directions; regulators receive evidence to find and stop sources inside the zone. Every alert and action is kept on the record. Reports for owners and funders come from the same record. 13. From order to operation · Maintain Keep the monitors quiet Monitors are checked for their own emissions, recalibrated on the agreed plan, and updated over fibre in rings. The interference database keeps every event, so trends and sources are visible over years. Maintenance history stays with each site for its whole life. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For astronomers and regulators Astronomers receive interference tags on their observations; observatory spectrum managers receive events and directions; spectrum regulators receive enforcement evidence; array operators receive site weather and timing, each tied to time, frequency and place. Every product can be traced back to its readings. [See the data products](https://observatory.global/data-products/) 15. Evidence Criteria the sky needs Interference is measured against the international protection criteria for radio astronomical measurements and the radio astronomy provisions of the Radio Regulations. Every sweep and event is kept, so observers, observatories and regulators share one record. The record is kept for as long as the duty lasts. Drawn againstRecommendation ITU-R RA.769 · ITU Radio Regulations, Article 29 16. What you get Spectrum and RF monitoring RF sensing in the band for interference, coexistence and spectrum planning. Delivered as managed service and data licence, for carriers, regulators, airports, venues. Scale: Regional. Service levels are written as numbers you can measure on your own dashboard. The same design repeats from the first site to the last. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan radio observatories and quiet zones 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 radio observatories and quiet zones. 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 contextRadio astronomy has protection criteria set by the international recommendation for radio astronomical measurements, bands allocated under the Radio Regulations, and in many countries a radio quiet zone around major observatories. Interference must be measured to show where criteria are exceeded and to find its sources. Hazards - Transmitters and devices inside the quiet zone - Satellites passing through the beam - Faulty electronics on the site itself - Weather that degrades observations at high frequencies - Timing errors that corrupt interferometry **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 | | --- | --- | --- | --- | | Interference across the radio spectrum | Monitoring receivers at the site and around the quiet zone | Continuous sweeps | 12 | | Site weather and precipitable water | Weather stations at the array | Every minute | 3 | | Time and frequency reference | Timing receivers and site clocks | Continuous | 1 | | Interference events and sources | Every detected event and its direction | Every event | 2 | **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 monitor: a wideband interference receiver and antenna with weather sensors and a timing receiver on a processing node. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A site: monitors at the array and around the quiet zone, linked by fibre to the observatory. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet An observatory's monitors processed as one, with an interference database for observers and regulators. [Managed offers →](https://observatory.global/industries/research/solutions/) 4. **04** Network Observatories share interference records with spectrum regulators and other observatories. [The open protocol →](https://observatory.global/protocol/) - **01** Compact weather station - **02** GNSS reference station (RTK) - **03** GPU edge server - **04** Fibre terminal - **05** Shelter Radio and links ### Fibre Inside the quiet zone, nothing transmits: every monitor reaches the observatory over fibre. Radio and links ### Public cellular Mobile monitoring vans report over cellular only from outside the zone boundary. Edge computeThe processing node sweeps the spectrum, compares it with the protection criteria, flags events, estimates direction and identifies known satellite passes, and tags observations with the interference present. PowerMains from the observatory with conditioned, shielded power, so the monitoring itself adds no interference. **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. Radio observatories and quiet zones: data path – of 06 01 Instruments Measurement with sensor identity andcalibration 02 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 03 Backhaul Commit with transactional outbox andpublish, delivered at least once 04 Site Consumer inbox deduplicates and applieseach record once into governed data 05 Data store Governed product through API, map orexport, correction-aware 06 Products VITA 49SigMFMQTT 07 Power and structure Wideband interference monitoringreceiver and antenna Not in the reference kit 01 Compact weather station SDI-12 · RS-485 · Ethernet 02 GNSS reference station (RTK) Ethernet · GNSS antenna · RS-232 ·1PPS/10 MHz 03 GPU edge server Ethernet · Fibre · PCIe · BMC ·1PPS/10 MHz 04 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Interference tags on observations Interference events and directions Enforcement evidence Site weather and timing 05 Shelter Ethernet Ethernet · MQTT 5 1PPS/10 MHz 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 | **Compact weather station** All-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 02 | **GNSS reference station (RTK)** Multi-constellation GNSS base station that streams corrections for real-time kinematic positioning. | EthernetGNSS antennaRS-2321PPS/10 MHz | NMEA 0183, NTP with NTS | 12 V DC | | 03 | **GPU edge server** Short-depth server with one or more accelerator modules for inference, training and AI-RAN shared compute at the edge. | EthernetFibrePCIeBMC1PPS/10 MHz | DMTF Redfish, IEEE 1588 PTP, MQTT 5 | AC mains, 48 V DC | | 04 | **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 | | 05 | **Shelter** Walk-in shelter or container with HVAC, fire detection and power distribution. | — | — | — | 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 zone and the bands The scope reads the observatory's bands, its quiet zone rules, past interference and the regulator's enforcement process. Nexus Observatory Inc. returns the monitor plan, processing design, interference database and a price per site and per year. The scope is agreed before any site work begins. 2 2. 02 Survey Survey the radio environment Crews survey the site and zone with a portable receiver: existing interference, candidate monitor sites with views across the zone, fibre routes and shielded rooms. Findings are recorded with spectra and directions. Findings shape the kit for each site before anything is built. 1 3. 03 Permits Regulator and site rules The spectrum regulator agrees how monitoring supports enforcement in the quiet zone, the observatory approves every installation for its own emissions, and land owners approve remote monitors. Every approval is kept with the site record. No crew goes to site before its approvals are in place. 4. 04 Build Build quiet Receivers, antennas and nodes are built and tested in a shielded chamber so they add no interference, calibrated across the bands, enrolled with their identities and run together before shipping. Nothing ships until the whole kit has passed its tests together. 5. 05 Install Install with fibre Crews mount monitor antennas, install receivers and nodes in shielded enclosures, lay or connect fibre and verify the installation adds nothing to the spectrum. Every monitor is photographed and recorded. Crews follow the site safety plan throughout the work. The site record is updated before the crew leaves. 6. 06 Commission Commission against known sources Each node proves its identity and time. Known test signals and satellite passes are detected and located, sweeps are compared with a reference receiver, and interference tags are checked against observers' own data. Acceptance is recorded with the owner before handover. 1 7. 07 Operate Tag and find interference Observers see the interference present during every observation; the observatory's spectrum manager sees events and directions; regulators receive evidence to find and stop sources inside the zone. Every alert and action is kept on the record. Reports for owners and funders come from the same record. 2 8. 08 Maintain Keep the monitors quiet Monitors are checked for their own emissions, recalibrated on the agreed plan, and updated over fibre in rings. The interference database keeps every event, so trends and sources are visible over years. Maintenance history stays with each site for its whole life. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Interference tags on observations** Astronomers - **Interference events and directions** Observatory spectrum managers - **Enforcement evidence** Spectrum regulators - **Site weather and timing** Operators of the array Integration - **Observatory systems** Tags join observation metadata in the observatory's archive. - **Regulator** Evidence is exported in the regulator's format. - **Scheduling** Weather and interference feed observation scheduling. Exchanged through VITA 49, SigMF, MQTT. **07** Questions buyers ask ## Before you scope it. Does monitoring add interference? No. Equipment is shielded and tested in a chamber before installation. Can it find a source? It estimates direction; the regulator investigates. Does it track satellites? Known passes are identified and tagged. Can astronomers flag data? Every observation carries its interference tags. **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** [Recommendation ITU-R RA.769: Protection criteria used for radio astronomical measurements](https://www.itu.int/) International Telecommunication Union 2. **2** [ITU Radio Regulations, Article 29: Radio astronomy service](https://www.itu.int/) International Telecommunication Union 3. **3** [WMO-No. 8: Guide to Instruments and Methods of Observation](https://library.wmo.int/) World Meteorological Organization **09** Related ## Use cases and solutions. [Solution Spectrum and RF monitoringRF sensing in the band for interference, coexistence and spectrum planning.Solutions for research →](https://observatory.global/industries/research/solutions/#rf-spectrum) [Solution Research site and instrument servicesSite power, connectivity, timing and operations for telescopes, flux towers and research stations.Solutions for research →](https://observatory.global/industries/research/solutions/#research-site-services) [Solution Timing and positioning integrityPTP grandmasters with GNSS holdover, interference detection and timing monitoring for networks and instruments.Solutions for research →](https://observatory.global/industries/research/solutions/#timing-positioning) **10** Research: specialized fields ## Other fields of this industry. [Specialized field Polar research stationsPower, fuel, environment, weather and communications at polar research stations, run so science continues through the winter and the station meets its environmental duties.The full field →](https://observatory.global/industries/research/polar-stations/) [Specialized field Field research campaignsDeployable instruments, mesh networking, drones and satellite backhaul for field campaigns, with data that are findable, documented and reusable from the first day.The full field →](https://observatory.global/industries/research/field-campaigns/) [Specialized field Geophysical observatoriesSeismic, magnetic, gravity and GNSS observatories in quiet vaults, run to the standards of the international data centres so their decades-long records are trusted worldwide.The full field →](https://observatory.global/industries/research/geophysical-observatories/) ### 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/)**Research** . Instruments for science, run like infrastructure.[Talk to us](https://observatory.global/contact/) Research - [Overview](https://observatory.global/industries/research/) - [Explainer](https://observatory.global/industries/research/explainer/) - [Specialized fields](https://observatory.global/industries/research/fields/) - [Use cases](https://observatory.global/industries/research/use-cases/) - [Solutions](https://observatory.global/industries/research/solutions/) - [Platforms](https://observatory.global/industries/research/platforms/) - [Resources](https://observatory.global/industries/research/resources/) - [Contact](https://observatory.global/industries/research/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/)