Simon

> Your peer count fluctuates a lot. What is your setup, is it local host or on a VPS? It runs on a vps with an independent elastic IP.

This is my lighthouse setup : lighthouse --datadir ${CONSENSUS_DIR} beacon_node --execution-endpoint ${EXECUTION_ENDPOINT} --execution-jwt ${JWT_SECRET_PATH} --checkpoint-sync-url ${CHECKPOINT_SYNC_URL} --http --http-address ${HTTP_ADDR} --http-port ${HTTP_PORT} --port ${PORT} --trusted-peers ${PEER_ID} --libp2p-addresses ${PEER} --debug-level ${DEBUG_LEVEL} --enr-address...

> > > Your peer count fluctuates a lot. What is your setup, is it local host or on a VPS? > > > > > > It runs on...

Actually, we have more than one nodes running on cloud servers. And we have a monitor programme. Once the lighthouse API eth/v1/node/health returned a non 200 code. We will restart...

> Do you have the logs when the health returned a non 200 code? It would help to identify the cause Yes. I uploaded it on discord.

Thank you @michaelsproul for helping me with my questions, I was going to post one myself. lol The mev-boost didnot restart at that time. @avalonche I post the mev debug...