There is little point in reporting errors. Apparently the admins are now aware of the problem and are trying to transfer osm.org under the wing of CloudFlare. It’s not easy to do this right away.
Ow, that’s why it showed me the Cloudflare verification page and the iD delayed to show the data (just now). Thanks for the heads up. I guess the yesterday’s maintenance annoyed the vandalists.
You probably just didn’t hit the timeout yet (which is fairly long), it is the nature of such things (load/bandwidth induced errors) that you will get different responses based on what just happened to fail for your specific API request.
I think it is more the long standing problem that the maintenance/issue alerts on social media from OSM ops are individually manually posted, so are literally the first thing to be a victim of a work/stress overload situation than any intent to favour a specific platform.
A cute cheeky response like that does not help a discussion at all. Its quite possible to announce something while its happening or after something has happend (to explain what happened).
I know, a situation like this is stressfull for all people involved, thats why there should be some kind of plan, what and where something should happen.
My post should probably have been worded differently so it does not sound that accusing - i’m really sorry for that. It was not meant to accuse anyone of anything.
Thanks for your answer SimonPoole. Its simply - OSM.org is down and i’m sure quite a lot of people would like to know what is happening
funny. there’s someone on the international telegram group claiming they can “end this right now” having written an email to the foundation using jamsboh@gmail.com
As you mentioned Mastodon, just to note for anyone who missed it in the earlier post by @whb, there is a thread started by the Ops Team account (not the main OpenStreetMap account). The earlier server maintenance was also announced on that account.