Open baknu opened 1 month ago
@mxsasha Not fully sure what triggers this message. Is it indeed Routinator starting up and feeding itself? And what would be an appropriate message? Something like: “Test not ready to run yet. Please try again later. Sorry for the inconvenience.”?
Yes, I think that's the best we can do. Other cause would be routinator breaking for some reason, but that is probably rare, we've never had that happen.
After a server reboot the following result was visible for a short while (probably because Routinator was not ready).