Blitzortung.org Forum
Station Data / Status issues - Printable Version

+- Blitzortung.org Forum (https://forum.blitzortung.org/mybb)
+-- Forum: Public Forums (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=29)
+--- Forum: Announcements ⚠️ (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=48)
+--- Thread: Station Data / Status issues (/showthread.php?tid=4287)



Station Data / Status issues - cutty - 2026-08-26

Station List, other data issues....
Message sent to Egon....
   


RE: Station Data / Status issues - K5OZ - 2026-08-26

Is map.blitortung.org down right now?


RE: Station Data / Status issues - cutty - 2026-08-26

(7 hours ago)K5OZ Wrote: Is map.blitortung.org down right now?
...included in "other issues".


UPDATE - cutty - 2026-08-26

Stations are showing as Idle, yet recent signals and Used/Involved statistics are still updating, and both the Blitzortung and LightningMaps.org maps appear to be displaying current lightning activity.

At the same time, operator-facing assets tied to station status, performance, and especially signal imagery appear to be unavailable.

That points more toward a station-status/operator-services problem than a failure of the core lightning signal/stroke-processing chain.

Definitely one for Egon/Tobi.


RE: Station Data / Status issues - cutty - 2026-08-26

**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.


RE: Station Data / Status issues - cutty - 2026-08-26

Issue seems resolved.