How is it now? It seems to have been aggravated for a while.
Iāve noticed that 2 of the 4 server of āprivate.coffeeā are not up-to-date: their ātimestamp_osm_baseā is ā2026-01-15T18:15:15Zā and ā2026-01-06T16:09:29Zā (today: 2026-01-17). The serverās names could be āh8ā and āh9ā. Selection seems to be RR (round-robin) DNS wise.
I created an issue some days ago.
N.B. Thatās why I did not yet switch to private.coffee for PTNAās on-demand analysis (GTFS vs OSM comparison)
FWIW the spike in " Netstat, established only" in August hasnāt reoccurred, but the Main Overpass API instance has been unreliable for some time now. Suggesting that people āUse alternative serversā is unhelpful as most peopleās use of the Overpass API isnāt direct; itās via third-party tools that either ājust failā or produce unpredictable results when the Overpass API theyāre using is unreliable**.
As I mentioned elsewhere Iāve ājust used something elseā when Iāve wanted to use āsomething like Overpassā (e.g. Postpass), but alas I suspect that @SimonPoole was right to say āThe surprising thing is more that the public Overpass instances have been able to stave off collapse for so longā.
How feasible would ārequiring people to be signed into OSM before using Overpassā be?
** and of course it really is the third-party tools that should catch this - some are better than others.
Please create a new post. It seems unrelated. Overpass API/status - OpenStreetMap Wiki
Agreed, for the nightly PTNA reports, Iām switching to planet extracts, no need for āup-to-date by minuteā data when mappers are asleep when their region gets analysed at 3AM their time.
For the other reports, the on-demand report, PTNA uses simple and more complex structured data
- boundary relations ā can be served by āpostpassā, Iām interested in their ways only
- route_master and route relations, āpostpassā is not suitable (I discussed this with Frederik)
- so I need āup-to-date by minuteā overpass data, as mappers what to see the positive impact of their work (uploaded some minutes ago)
But these details are off-topic.
Iāve created a new thread - even though people observe it as the same issue, the cause of the August 2025 issue was distinct.
This is a debatable claim. It seems to me that the problem lies elsewhere. Letās just look at the error message users see for Overpass Turbo:
Itās bad. Overpass Turbo could check the HTTP error code and show a link to https://osm.wiki/Overpass_API#Public_Overpass_API_instances if itās 5xx.
My experience with people using Overpass Turbo is that they are hearing about other servers for the first time.
How would that help? That is a list of Overpass API endpoints, not Overpass Turbo ones. Pointing a web browser at one of those just gives:
The data included in this document is from www.openstreetmap.org. The data is made available under ODbL.
Error: encoding error: Your input contains only whitespace.
Letās imagine Iāve just got the Overpass API error above in Overpass Turbo. What should I do to run the same Overpass Turbo query against a different server?
Edit: Until @Mateusz_Koniecznyās post below I had no idea that any Overpass Turbo instance could be pointed at any other Overpass API one. I suspect that I wasnāt the only person in OSM who didnāt know that ![]()
change it in Overpass Turbo settings, accessible from top bar, second button from right
![]()
then near top in window that will appear currently the second line allows you to try on a different server
the problem is that I found no server that would be up to date and working well, when I was looking for alternatives
I can only echo āThe surprising thing is more that the public Overpass instances have been able to stave off collapse for so longā.
Thatās a good point. Iāve edited this wiki page to make those links unclickable.
But I just wanted to get the idea across. We need to show the user what they can do: use a different frontend, change settings, and so on.
Or optimize the query. I found an interesting tip from the documentation in the previous thread: Commons
The server admits a request if and only if it is going to use in both criteria at most half of the remaining available resources.
For the maximum memory usage, the default value is 512 MiB.
Now Iāve experimented a bit and realized that for many requests [out:json][maxsize:16Mi] is enough for me and Iāve never received a 504. You can even get away with 1Mi if youāre asking for something like node[...]({{bbox}}). 64Mi was enough for me to request all buildings in St.Petersburg (but as expected, Overpass Turbo froze for me:)
Perhaps this is just a hack for the current rate limit mechanism, and if everyone defaults to 64Mi, weāll end up back where we are. But perhaps this is low-hanging fruit for optimization.
But itās worth noting that this method has its problems. For example, requests to maps.mail.ru will be blocked by Tracking Protection in Firefox. Also on the list is a long-time non-operating overpass.openstreetmap.ru
Well itās certainly not getting any better: osm db request count (Munin :: localdomain :: localhost.localdomain :: osm db request count)
There seems to have been a significant uptick in the abuse in November.
I feel we may be in the era of if you need Overpass for your process youāre going to have to run your own. I know Iāve had to set up my own AU instance to keep my scripts from constantly breaking.
EDIT: Ha, turns out I just repeated what Simon already said Undiscussed mass edits of sport=rugby_union and sport=rugby_league - #8 by SimonPoole

