--- title: "Timing integrity monitoring | Nexus Observatory" description: "Power grids, telecom networks, financial markets and broadcasters depend on precise time, mostly from satellite navigation." url: https://observatory.global/industries/resilience/timing-integrity/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Civil resilience](https://observatory.global/industries/resilience/) / [Specialized fields](https://observatory.global/industries/resilience/fields/) / **Timing integrity** # Time that holds when the satellites go quiet. Power grids, telecom networks, financial markets and broadcasters depend on precise time, mostly from satellite navigation. Jamming, spoofing or a satellite fault can take it away. Reference clocks with holdover, monitoring of every timing source and time delivered over terrestrial networks keep critical systems on time. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Civil resilience **Measurements**: 4 **Sources cited**: 4 1. Civil resilience · Timing integrity Hidden dependence on satellites Grids, telecom networks, markets and broadcasters all need precise time, and most take it from satellite navigation. Jamming near a port, spoofing that moves time silently or a satellite system fault can take it from every receiver at once. Governments ask operators to understand the dependence and plan for its loss. 2. What is measured Every source compared Timing receivers watch satellite signal quality and interference at each reference site. Reference clocks with holdover oscillators keep time independently, and precision time protocol clocks at substations and cell sites measure the time error that actually reaches the systems that use it. InstrumentsTiming receivers · Reference clocks · Network time error probes 3. The base node Trust decided at the site The node compares satellite time with the reference clock and terrestrial time each second. Sudden offsets and degraded signals mark jamming or spoofing; the clock is switched to holdover, the decision is logged, and the remaining time within limits is reported to the operator. 4. Radio and links Time over the network Time travels over the operator's fibre with the precision time protocol, so delivery points do not depend on their own satellite receivers. Microwave carries time to sites without fibre, with its delay measured and corrected. Monitoring travels through a security gateway. LinksFibre · Microwave 5. How it works From jamming to holdover A vehicle with a jammer parks near a substation. The timing receiver's signal quality collapses and its time jumps; the node rejects it, the reference clock holds, and substations keep receiving time over fibre. The operator sees the event, the remaining holdover and the location of the interference. 6. From order to operation · Order Map the timing dependence The scope maps every system that needs time, where its time comes from, how accurate it must be and what happens when it is lost. Nexus Observatory Inc. returns the reference sites, holdover design, monitoring and delivery over the network, and a price per site and per year. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey for interference Crews survey candidate reference sites for sky view, nearby roads and ports where jamming is common, secure rooms and power, and the network paths that will carry time. A spectrum scan records interference at each candidate. Findings shape the kit for each site before anything is built. 8. From order to operation · Permits Security and change control Reference sites are placed in secure rooms under the operator's access rules, and connecting timing to production networks goes through change control. Interference found during the survey is reported to the spectrum regulator, and every approval is kept with the site record. 9. From order to operation · Build Build and characterise clocks Reference clocks are characterised in the shop for their holdover drift, receivers are tested against simulated jamming and spoofing, and nodes are enrolled with their identities. Every kit runs together for days so its behaviour is known before it ships. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install antennas and clocks Crews mount antennas where they see the sky but not the road, install clocks, receivers and nodes in secure rooms, and connect time to the network's precision time protocol chain. Cable delays are measured and recorded for each antenna. Crews follow the site safety plan throughout the work. 11. From order to operation · Commission Commission against a time laboratory Each node proves its identity. Time is compared with a traceable reference, holdover is tested by removing the antenna for a planned period, and time error is measured at delivery points along the network. Results are recorded for each site. 12. From order to operation · Operate Watch every source The operator sees every reference site, its sources, signal quality, interference events and time error at delivery points. When jamming appears, clocks hold and the view shows how long they will stay within limits. Every event is kept on record. 13. From order to operation · Maintain Retest holdover Holdover is retested on the agreed plan, oscillators are replaced as they age, software updates roll out in rings, and interference patterns are reviewed with the regulator. Every change, test and event is kept with the site record. Maintenance history stays with each site for its whole life. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For operations, security and planners Network and grid operations receive time error across the network; security teams and spectrum regulators receive jamming and spoofing events; operations receive holdover time remaining during interference; resilience planners receive the timing dependence map, each tied to the site and time. [See the data products](https://observatory.global/data-products/) 15. Evidence Time you can prove Reference clocks meet the primary reference clock recommendation, time is carried over the telecom timing profile of the precision time protocol, and the programme answers the government call to use satellite timing responsibly. Every comparison, holdover and interference event is logged and kept. Drawn againstITU-T G.8272 · ITU-T G.8275.1 · IEEE 1588 · Executive Order 13905 16. What you get Timing and positioning integrity PTP grandmasters with GNSS holdover, interference detection and timing monitoring for networks and instruments. Delivered as hardware + software and managed service, for carriers, utilities, financial infrastructure, observatories. Scale: National timing fabrics. 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 timing integrity 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 timing integrity. 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 contextCritical infrastructure has grown dependent on satellite time. Governments have asked operators to understand that dependence and to use timing responsibly; primary reference clocks and telecom timing profiles are defined in international recommendations; and precision time is carried over networks by the precision time protocol. Hazards - Jamming near roads, ports and borders - Spoofing that moves time without raising an alarm - Satellite system faults affecting every receiver at once - Clocks that drift silently after losing their reference - Timing chains no one has mapped end to end **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 | | --- | --- | --- | --- | | Satellite signal quality and interference | Timing receivers at every reference site | Continuous, events on degradation | 1 | | Time offset between independent sources | Satellite, terrestrial and local clock comparisons | Every second | 2 | | Holdover performance | Reference clocks after loss of satellite time | Continuous during holdover | 2 | | Network time error at delivery points | Precision time protocol clocks at substations and cell sites | Continuous | 34 | **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 timing point: a timing receiver, a reference clock with a holdover oscillator and a node that compares every source. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A site: the timing point in a secure room, antennas placed against interference and time delivered over the operator's network. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every timing site of an operator monitored as one fleet, with one view of time error across the network. [Managed offers →](https://observatory.global/industries/resilience/solutions/) 4. **04** Network Operators, time laboratories and regulators compare time across organisations and share interference reports through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** GNSS reference station (RTK) - **02** Edge node (Wedge) - **03** Zero-trust gateway - **04** Fibre terminal - **05** Point-to-point microwave - **06** Shelter Radio and links ### Fibre Time travels over the operator's fibre with the precision time protocol, independent of satellites at the delivery point. Radio and links ### Point-to-point microwave Microwave carries time to sites without fibre, with its delay measured and corrected. Edge computeThe node compares satellite time with the reference clock and terrestrial time, detects jamming and spoofing from signal quality and sudden offsets, switches the clock to holdover when the satellite source is untrusted, and logs every decision. PowerTiming sites run from protected DC with batteries that outlast the holdover period, because a clock that loses power loses its time. **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. Timing integrity: 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 IEEE 1588 PTPNTP with NTSITU-T G.8275.1 07 Power and structure 01 GNSS reference station (RTK) Ethernet · GNSS antenna · RS-232 ·1PPS/10 MHz Primary reference time clock withholdover oscillator Not in the reference kit 02 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 03 Zero-trust gateway Ethernet · Fibre 04 Fibre terminal Fibre · Ethernet 05 Point-to-point microwave Ethernet · Fibre Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Time error across the network Jamming and spoofing events Holdover time remaining Timing dependence map 06 Shelter Ethernet · ntp-nts Ethernet Fibre · ptp Ethernet · ptp Ethernet Fibre Microwave link 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 | **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 | | 02 | **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 | | 03 | **Zero-trust gateway** Gateway that terminates encrypted tunnels, enforces segmentation and gates every flow by identity and policy. | EthernetFibre | — | 12 V DC, AC mains | | 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 | **Point-to-point microwave** Licensed or licence-exempt point-to-point radio link between two sites with line-of-sight. | EthernetFibre | IEEE 1588 PTP | PoE, 48 V DC | | 06 | **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 Map the timing dependence The scope maps every system that needs time, where its time comes from, how accurate it must be and what happens when it is lost. Nexus Observatory Inc. returns the reference sites, holdover design, monitoring and delivery over the network, and a price per site and per year. 1 2. 02 Survey Survey for interference Crews survey candidate reference sites for sky view, nearby roads and ports where jamming is common, secure rooms and power, and the network paths that will carry time. A spectrum scan records interference at each candidate. Findings shape the kit for each site before anything is built. 3. 03 Permits Security and change control Reference sites are placed in secure rooms under the operator's access rules, and connecting timing to production networks goes through change control. Interference found during the survey is reported to the spectrum regulator, and every approval is kept with the site record. 4. 04 Build Build and characterise clocks Reference clocks are characterised in the shop for their holdover drift, receivers are tested against simulated jamming and spoofing, and nodes are enrolled with their identities. Every kit runs together for days so its behaviour is known before it ships. 2 5. 05 Install Install antennas and clocks Crews mount antennas where they see the sky but not the road, install clocks, receivers and nodes in secure rooms, and connect time to the network's precision time protocol chain. Cable delays are measured and recorded for each antenna. Crews follow the site safety plan throughout the work. 4 6. 06 Commission Commission against a time laboratory Each node proves its identity. Time is compared with a traceable reference, holdover is tested by removing the antenna for a planned period, and time error is measured at delivery points along the network. Results are recorded for each site. 3 7. 07 Operate Watch every source The operator sees every reference site, its sources, signal quality, interference events and time error at delivery points. When jamming appears, clocks hold and the view shows how long they will stay within limits. Every event is kept on record. 1 8. 08 Maintain Retest holdover Holdover is retested on the agreed plan, oscillators are replaced as they age, software updates roll out in rings, and interference patterns are reviewed with the regulator. Every change, test and event is kept with the site record. Maintenance history stays with each site for its whole life. 2 **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Time error across the network** Network and grid operations - **Jamming and spoofing events** Security teams and spectrum regulators - **Holdover time remaining** Operations during interference - **Timing dependence map** Resilience planners Integration - **Network management** Timing alarms reach the operator's network management system through its own interfaces. - **Grid control** Substation clocks receive time over the network for protection and measurement. - **Regulator** Interference events are exported for reporting. Exchanged through IEEE 1588 PTP, NTP with NTS, ITU-T G.8275.1. **07** Questions buyers ask ## Before you scope it. What happens when satellites are jammed? Clocks hold time and the view shows how long they stay within limits. Can it detect spoofing? Sudden offsets between independent sources raise an alarm. Do we need new fibre? No. Time travels over the existing network where it supports the protocol. How long does holdover last? It depends on the clock chosen, measured before installation. **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** [Executive Order 13905: Strengthening National Resilience Through Responsible Use of Positioning, Navigation, and Timing Services](https://www.federalregister.gov/) United States Federal Register · 2020 2. **2** [ITU-T G.8272: Timing characteristics of primary reference time clocks](https://www.itu.int/) International Telecommunication Union 3. **3** [ITU-T G.8275.1: Precision time protocol telecom profile for phase/time synchronization with full timing support from the network](https://www.itu.int/) International Telecommunication Union 4. **4** [IEEE 1588: Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems](https://standards.ieee.org/) IEEE Standards Association **09** Related ## Use cases and solutions. [Solution Timing and positioning integrityPTP grandmasters with GNSS holdover, interference detection and timing monitoring for networks and instruments.Solutions for civil resilience →](https://observatory.global/industries/resilience/solutions/#timing-positioning) [Solution Operational-technology assurance for observing sitesIdentity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits.Solutions for civil resilience →](https://observatory.global/industries/resilience/solutions/#ot-site-assurance) **10** Civil resilience: specialized fields ## Other fields of this industry. [Specialized field Critical site securityPerimeter, intrusion and operational-technology monitoring for substations, pumping stations and other unstaffed critical sites, so operators see a threat to the site and its control systems at once.The full field →](https://observatory.global/industries/resilience/site-security/) [Specialized field Backup power at critical sitesGenerators, fuel, batteries and transfer switches at hospitals, water plants and telecom hubs, monitored and tested so backup power starts when the grid fails.The full field →](https://observatory.global/industries/resilience/backup-power/) [Specialized field Northern and Arctic observingWeather, permafrost, ground movement and river and lake ice stations for northern civil authorities, built for polar night, deep cold and satellite-only backhaul.The full field →](https://observatory.global/industries/resilience/arctic-observing/) ### 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/)**Civil resilience** . Infrastructure that reports before it fails.[Talk to us](https://observatory.global/contact/) Civil resilience - [Overview](https://observatory.global/industries/resilience/) - [Explainer](https://observatory.global/industries/resilience/explainer/) - [Specialized fields](https://observatory.global/industries/resilience/fields/) - [Use cases](https://observatory.global/industries/resilience/use-cases/) - [Solutions](https://observatory.global/industries/resilience/solutions/) - [Platforms](https://observatory.global/industries/resilience/platforms/) - [Resources](https://observatory.global/industries/resilience/resources/) - [Contact](https://observatory.global/industries/resilience/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/)