Posts: 59
Threads: 16
Joined: 12/2017
2026-08-01, 14:48
(This post was last modified: 2026-08-02, 02:25 by W2PJ-WX.)
In the last two days I am getting an error loading this statistics web page:
https://www.lightningmaps.org/blitzortun...o_sid=2110
I get the error ""Bad Gateway :: Code 502". "Sorry, there was an error. Please try again later."
Sometimes a get a partial load of data, but never the complete page.
Internet (Gemini AI), suggests this is a server problem? Anyone else seeing this problem as well? How does it get resolved?
Thanks
Pete - W2PJ
Posts: 59
Threads: 16
Joined: 12/2017
In the last two to three days, I am getting an error loading this statistics web page:
"https://www.lightningmaps.org/blitzortung/america/index.php?bo_page=statistics&bo_show=station&bo_sid=2110"
I get the error ""Bad Gateway :: Code 502" "Sorry, there was an error. Please try again later."
Sometimes a get a partial load of data, but never the complete page.
Internet (Gemini AI), suggests this is a server problem? Anyone else seeing this problem as well? How does it get resolved?
Thanks
Pete - W2PJ
Posts: 1,974
Threads: 64
Joined: 07/2013
2026-08-02, 10:49
(This post was last modified: 2026-08-02, 10:52 by cutty.)
(2026-08-02, 02:23)W2PJ-WX Wrote: In the last two to three days, I am getting an error loading this statistics web page:
"https://www.lightningmaps.org/blitzortung/america/index.php?bo_page=statistics&bo_show=station&bo_sid=2110"
I get the error ""Bad Gateway :: Code 502" "Sorry, there was an error. Please try again later."
Sometimes a get a partial load of data, but never the complete page.
Internet (Gemini AI), suggests this is a server problem? Anyone else seeing this problem as well? How does it get resolved?
Thanks
Pete - W2PJ
Works for me. Maybe check your browser cache? NOTE that Lightningmaps.org does have caveats regarding data. " Please note that the data displayed here might be outdated or wrong! These pages will be replaced by new ones in the future. "
Posts: 1
Threads: 0
Joined: 11/2025
A 502 error usually points to a temporary problem between servers rather than something on the local browser side. Since the page only loads partially for Pete, it could also be related to a backend request timing out or failing intermittently.
If clearing the cache makes no difference, I would try the same URL from another connection or device and see whether the behavior is identical. If it is, waiting for the server side to recover is probably the only real option.
