Power Grids On 5 Continents Pulse Every 60s. Scientists Think They Know Why
5 77"ScienceAlert is reporting that researchers may have finally determined why, for many years, power grids around the world have been pulsing every 60 seconds," writes longtime Slashdot reader fahrbot-bot. The likely culprit? Uninterruptible power supplies running routine battery checks. From the report: Every minute, some uninterruptible power supplies perform routine battery checks, creating small but measurable surges in electricity demand. And it's like clockwork. "Even benign control routines can become systemically relevant when many devices act coherently," writes a team led by physicist Dirk Witthaut of the University of Cologne, Germany, in a paper published in Nature Energy. "Unintended synchronization can generate recurrent and potentially amplified oscillatory behavior in large-scale cyber-physical energy systems."
To figure it out, Witthaut and his colleagues analyzed high-resolution electricity measurements from buildings at the Forschungszentrum Julich research campus in Germany. [... they found that] the 60-second pattern appeared in four buildings, all of which contained uninterruptible power supplies. None of the buildings they measured without these systems showed the same pattern. Following the electrical signals more closely, the researchers detected tiny bursts of current from the batteries at precisely one-minute intervals. They were able to trace the resulting fluctuations through one building's electrical system, all the way to the connection with the public high-voltage grid.
The manufacturer subsequently confirmed the culprit's identity -- routine battery self-tests, conducted automatically by the systems' management software. But why would equipment in different buildings, let alone different countries, be doing this at the same time? The answer appears to lie in the clocks. Digital devices can synchronize their internal clocks using external time signals, meaning that independently operating systems can end up performing their scheduled tasks together. Individually, these small checks are insignificant. But when enough devices act in synchrony, their combined electricity demand can produce a measurable effect across an entire power grid.
5 comments
Re:Smdh (Score: 5, Informative)
by fahrbot-bot ( 874524 ) on Thursday November 12, 2026 @03:02AM (#66420774)
The straightforward solution is for the UPS manufacturers to jitter the test time and it becomes a total non-issue.
From TFA:
Fortunately, the solution may be relatively straightforward, at least for big batteries and backup systems. Rather than having thousands of devices perform the same task at the same moment, manufacturers could introduce small variations into their software schedules, preventing the minutely pile-up.
Indeed, they have already contacted the manufacturer of one of the systems they identified, and the company issued a software update that relaxed the strict periodicity of its system checks.
Coherence (Score: 5, Interesting)
by pz ( 113803 ) on Thursday November 12, 2026 @06:50AM (#66420913)
When I was working for a startup in the early 2000s, we had our own servers. We were growing, so were adding servers at a pretty good clip. After one particular expansion, all of a sudden, Saturday night at 3 am, we blew breaker. No one had a good explanation, but the sysadmins were not happy about needing to go to the office in the middle of the night to fix things up.
A week later, the same thing happened. I suggested that it was the RAID check kickoff that might be doing it. And, indeed, it was. A couple of dozen servers all seeking their drives at once was too much for the circuits they were on. Staggering the startup time fixed it.
Coherence can be good, like when you're rowing crew, or bad, like when you have dozens of drives all drawing max power. Or, from the summary, gazoober UPS systems doing a battery check.
Re: Coherence (Score: 5, Informative)
by topham ( 32406 ) on Thursday November 12, 2026 @07:33AM (#66420957)
Maximum amperage draw for 1/10th of a second is not usually taken into account, breakers don't usually blow that fast because of a current spike. (Those numbers are usually not on the specification sheet either.)
The maximum load is calculated over a period of time, not a very short period of time. It is in this fuzzy gap that issues like this arrive.
Blast from the past (Score: 5, Interesting)
by dsgrntlxmply ( 610492 ) on Thursday November 12, 2026 @07:25AM (#66420945)
In the 70s I wrote embedded asm code for networked terminals. There were around 400 terminals. They checked with a central system every night at midnight for software updates, and at some other interval for clock sync. Unfortunately, there was not much relative drift in the terminal clocks, so the central system began having overload failures at midnight. We ended up putting a request time spreading factor into the terminal's update request code.
Lessons from the physical world - 1831 bridge fail (Score: 5, Informative)
by mccalli ( 323026 ) on Thursday November 12, 2026 @08:21AM (#66420987)
This is eerily similar to the marching soldiers' bridge collapse [wikipedia.org] - Broughton Bridge in 1831, often misattributed to Napoleon but happened after his reign.
Lessons weren't learned 180 years later either, for the Milllennium Suspension Bridge [wikipedia.org], which I happened to work next to at the time and watched the construction and failure unfold. People tend to walk in sync. When things happen in sync, a resonant pattern emerges. It's true for people crossing bridges. It's true for people synchronising machines to exact clocks and nice rounded-off times as well.