Overpass API Performance Issue?

Help and support
1

Has anyone else experienced extremely slow response times from the Overpass APIs today? My queries are taking up to a minute to return data. Is there a known issue with the server?

[out:json][timeout:50];
// Search radius: 5000 meters
(
  // Hospitals under construction or proposed
  node(around:5000, 51.5769, -0.0458)[amenity=hospital][construction];
  way(around:5000, 51.5769, -0.0458)[amenity=hospital][construction];
  node(around:5000, 51.5769, -0.0458)[amenity=hospital][proposed];
  way(around:5000, 51.5769, -0.0458)[amenity=hospital][proposed];
  // Schools under construction or proposed
  node(around:5000, 51.5769, -0.0458)[amenity=school][construction];
  way(around:5000, 51.5769, -0.0458)[amenity=school][construction];
  node(around:5000, 51.5769, -0.0458)[amenity=school][proposed];
  way(around:5000, 51.5769, -0.0458)[amenity=school][proposed];
  // Universities under construction or proposed
  node(around:5000, 51.5769, -0.0458)[amenity=university][construction];
  way(around:5000, 51.5769, -0.0458)[amenity=university][construction];
  node(around:5000, 51.5769, -0.0458)[amenity=university][proposed];
  way(around:5000, 51.5769, -0.0458)[amenity=university][proposed];
  // Generic under-construction or proposed buildings
  node(around:5000, 51.5769, -0.0458)[building=construction];
  way(around:5000, 51.5769, -0.0458)[building=construction];
  node(around:5000, 51.5769, -0.0458)[construction];
  way(around:5000, 51.5769, -0.0458)[construction];
  node(around:5000, 51.5769, -0.0458)[proposed];
  way(around:5000, 51.5769, -0.0458)[proposed];
);
// Output details
out body;
>;
out skel qt;
1 Like
2

Yes, there are an abnormal number of requests to the main server: network (Munin)

Use alternative servers: Overpass API - OpenStreetMap Wiki

5 Likes
3

So is it! I wondered why MapRoulette did not want to rebuild my tasks and finished with a timeout… DoS? :angry:

1 Like
4

Thank you for reporting the issue.

The event is most likely not an attack but rather a bug in the resource distribution that is triggered by a certain pattern of access that disregarding the usage policy. So far all overuse had been rejected automatically, hence apparently the specific pattern is happening the first time.

I’ve deployed a hotfix of which I hope that it fixes the bug. We will see after a couple of days whether this gets the greedy guys locked out.

5 Likes