Openstreetmap inspector routing view update broken

@Nakaner : Could you please check the update procedure for the OSMI routing view? There seems to be some server problem as the data does currently not update and the shown date consists of two entries:

thank you!

I emailed Geofabrik about the problem yesterday.

I have fixed this now, sorry for the interruption.

We’re playing around with an “alpha” version (more like a prototype) of new vector-based OSMI. You can look at that on (no https) OSMI Test - there’s still much to do before it can replace the old OSMI but we’ll get there eventually. It was in the course of configuriging the automatic updates for that new thing when I broke the routing layer update.

I have fixed this now, sorry for the interruption.

Thank you for caring. I confirm that the data updated once successfully. But I would like to ask to check it again. Yesterday around 20:00 CET I fixed a lot of connectivity issues. These still show up now with the second date being 2026-03-19 01:00 (UTC).

And could you please also check why there are still two dates being shown under “Data from”? This seems to be an unrelated problem because I don’t see a point in indicating two dates.

I can confirm I see the same problems as ratrun. At least some of the issues I’ve corrected remain as problems the next day. I also see the same issue with the dates.

It appears my previous fix was not as permanent as I would have wished it to be. Tried again on the 23rd and I now see an update coming through around 19Z. Fingers crossed. The date bug should now be fixed as well. Showing more than one date is not impossible since the routing view is calculated for a western and eastern half of the planet separately so it is possible to have an older Eurasia and a newer rest-of-world and vice versa, but this should only ever last for a couple of hours at most.

Thanks woodpeck, thats very much appreciated. I can see a lot of new data and it looks like my corrected problems are now removed.

About the dates though, this morning says “Data from 2026-03-04 12:00 .. 2026-03-23 09:00 (UTC)”, thats a spread of 19 days. I think the glitch might be inadvertantly keeping the first date which is when the problems first started.