India just took its national time signal off GPS
CSIR-NPL and ISRO commissioned a CERN-derived precision timing network in Bengaluru, distributing Indian Standard Time over fibre instead of satellites. GPS spoofing is a documented attack surface. This removes it for anything that needs a timestamp it can trust.
India just gave banking, telecom, and power grids a time signal that GPS jamming cannot touch.
India commissioned a demonstration network in Bengaluru this week that distributes Indian Standard Time over fibre-optic cable instead of GPS, using timing technology built at CERN for particle physics. The point is not precision for its own sake. It is removing a single point of failure that almost every piece of software with a clock quietly depends on.
What actually launched
The network runs out of the Regional Reference Standard Laboratory in Bengaluru, a joint effort between the Department of Consumer Affairs, CSIR-National Physical Laboratory, and ISRO, launched by union minister Pralhad Joshi under the government's One Nation, One Time initiative. It uses White Rabbit, a timing protocol that combines Precision Time Protocol with Synchronous Ethernet over fibre to hit sub-nanosecond synchronisation, traceable back to India's own time authority, UTC(NPLI), rather than to a satellite constellation.
Why GPS timing is a real weak point
Most software that needs a synchronised clock, from NTP servers to distributed databases, ultimately traces its time back to GPS-disciplined clocks. GPS signals arrive at a receiver extremely weak, which makes them realistically jammable and spoofable from a cheap ground transmitter, not just a theoretical attack. Shipping and aviation have both logged real GPS spoofing incidents that threw off navigation systems. A timing source depending on the same signal path is exposed to the same failure mode, just applied to clocks instead of positions.
Why a build studio cares
A fibre-traceable time source that cannot be jammed from a rooftop matters for exactly the kind of systems we wire up for clients: distributed transaction logs, audit trails, OTP and session expiry windows, and payment ordering on rails like UPI all depend on clocks agreeing with each other. Clock drift and spoofed timestamps are a real, if underrated, bug class in distributed systems, the kind that surfaces as a security incident rather than a crash. If this network's timing service becomes broadly reachable the way public NTP pools are today, it is a materially harder target than GPS-derived time for anything hosted in India that cares about timestamp integrity.
Next step: see Business Standard's coverage of the launch and LatestLY's explainer on the underlying technology. If clock synchronisation or timestamp integrity matters for a build you are running in India, write to us at hello@gattyworks.com.