**Update:** This looks broader than just the station-status display.
Looking at the full status page, **Europe 1, North America 1, and Africa 1 all stopped updating at about 22:52 UTC Aug. 25**. Their station statistics are now zero/stale.
Meanwhile **Europe 2, Europe 3, and North America 2 are continuing to update normally**, with current Signals/Valid/Involved/Used data.
So this appears to affect the common **“1” server/computation group**, while the secondary servers remain operational. That would also explain why the public lightning maps are still showing current strokes. BUT it may be that the MAPS are not generating strokes from the R1 servers
iBOD itself also appears to be receiving and forwarding signals normally, so the problem seems to be farther downstream in the primary computation/services side.
That 08:25 ±22:52 UTC timestamp may be useful for checking logs.
Looking at the full status page, **Europe 1, North America 1, and Africa 1 all stopped updating at about 22:52 UTC Aug. 25**. Their station statistics are now zero/stale.
Meanwhile **Europe 2, Europe 3, and North America 2 are continuing to update normally**, with current Signals/Valid/Involved/Used data.
So this appears to affect the common **“1” server/computation group**, while the secondary servers remain operational. That would also explain why the public lightning maps are still showing current strokes. BUT it may be that the MAPS are not generating strokes from the R1 servers
iBOD itself also appears to be receiving and forwarding signals normally, so the problem seems to be farther downstream in the primary computation/services side.
That 08:25 ±22:52 UTC timestamp may be useful for checking logs.
