More of an inquiry than an issue:
Prior to v15.0, Routinator sent a HTTP/1.1 503 Service Unavailable before the first fetch completed.

The change log references:
Added a quick initial run after starting the server which only uses stored data and aborts if any required data hasn’t been requested before to deal with configuration changes. This will shorten the wait time for an initial data set when restarting Routinator. (#1057)

Now, it immediately returns a 200 OK immediately. I believe this was the PR that changed this behavior, which addressed slower startup times in this issue.

Is there an endpoint that reflects the original behavior? For context, I relied on that endpoint for healthchecking.