Liveness endpoint false negative about nimbus-eth2 HOT 2 OPEN

We've thoroughly investigated this report and the most likely explanation is that our public API server was overloaded at the time which has resulted in delays in the processing of incoming attestations. We recommend testing the liveness endpoint against your own private Nimbus instance which cannot be affected by requests from other users.

from nimbus-eth2.

In the ticket I used the Nimbus public endpoint in order to have a self-contained reproduction example.
But I actually used Chainstack service (which also use Nimbus BN under the hood).

==> I guess the overloading issue could be the same using Chainstack than Nimbus public endpoint however.

To give you a little bit more context, I'm building this: https://github.com/kilnfi/eth-validator-watcher

from nimbus-eth2.