In the case of a search service disruption the status updates will be shown here.
05 Jun 26: there was an initial issue with v7.8.1 release because the newer protocol server version was taken by google chrome from cache rather than downloaded for real so I reversed the release temporarily since it got me confused until I figured out the banal cause.
I attempted a search a few minutes ago and I got the following message back.
Incase the image does not show. It says:
Search failed on all servers [configuration ok] A connection attempt failed because the connected party
did not respond after a period of time, or
The router failed, it has been replaced a few hours ago, the server pings the website with the new ip, so if nothing extreme has been posted headers should be up to date.
The search service will be accessible when the incoming ports are configured, hopefully it won't take long.
It should work now, header download was suspended as no headers were coming to have an option to change server settings to prevent unnecessary newsgroup resets and excessive header download later, but it is fast to bring them up-to-date.