Can't view relation history - server error

I can’t access this URL: https://www.openstreetmap.org/relation/207359/history

This is Los Angeles, which was recently vandalized and reverted. I wanted to take a look at the vandalized tags, but instead I encounter a server error. Most of the time it shows a Cloudflare error page, but now I got this message:

Timeout Error
Sorry, the history of the relation with the id 207359 took too long to retrieve.

Is it just me?

Edit: this is the Cloudflare error I get most of the time:

It takes ages (29.04 seconds), but it works:

1 Like

What version is it at?.. See mcliquid got it and it shows v241. Yes, I have this at times when there’s many nodes, members, and many versions to boot in a relation (route relation or multipolygon to name a few.).

I’d try using tools like OSM Deep History for viewing items with a lengthy history.

3 Likes

Interesting. Does it also work without better-osm-org?

I see. Shouldn’t osm.org be able to show something, or at least fail more gracefully?

Here in Private Tab without plugins:

Took 31 seconds (have a 500 MBit cable connection)

1 Like

I see. It’s weird because I get actual errors, it’s not just me being impatient. But I guess if the connection is slower (I’m on 5G right now) it could take longer and hit a timeout.

I’ll leave it to you guys to determine whether this is an issue or not, but I consider my question answered.

Specifically for dealing with name vandalism, I created a version here. The differences are that it only looks at tags, but also links to changeset comments, achavi, etc.)

Being on copper, a mile away from the supposed FTTC, just have 12Mb download at best. Often I use my mobile hotspot which gives 80Mb, but still objects like the Adriatic Sea multipolygon (now deleted courtesy of a DWG member and replaced by the restored place node), took me an hour to fetch piece by piece before being able to confirm that edits/repairs restored the relation to proper closed state. Such objects I save to a local datafile but still I refresh it times out. On a 0.5Gb line that would probably not be the case.