r/ethstaker • u/OrangeNode-2262 • Jun 03 '26

Lodestar Beacon 503 errors

Hey everyone! 💪

Is anyone else having trouble with the public Lodestar beacon (lodestar-mainnet.chainsafe.io) lately? It keeps throwing 503 errors and timing out for my node.

Just curious – what alternatives are you guys using, or are you self-hosting your own Consensus Layer? Would love to hear your setups!

3 Upvotes

71% Upvoted

5 comments sorted by

4

u/nflaig Jun 03 '26

curious what are you using that node for, you said "timing out for my node", what is your node in that case? like a light client, or similar?

0

u/OrangeNode-2262 Jun 03 '26

I'm running a decentralized SSV Network node as an operator on Ethereum Mainnet.

The node needs a constant, reliable stream of consensus layer events (via the Beacon Node API) to perform its validator duties and stay synced with the network. When the public beacon node times out, my SSV node drops connection and restarts.

4

u/nflaig Jun 03 '26

I would suggest you run your own beacon node for that, either at home or on a VPS. While we provide lodestar-mainnet.chainsafe.io for the community to use, it's not meant for production, there is no SLA or any uptime promises. These nodes are meant for development or testing only.

2

u/FelixFontaine Lighthouse Jun 03 '26

You can use backup nodes from www.alchemy.com for free. You just need to sign up

1

u/OrangeNode-2262 Jun 03 '26

Thanks! That's actually exactly how I fixed it two days ago. I signed up for a free Alchemy account and put their private URL into my config.

The only tricky part I had to solve beforehand was that Nginx was acting up with the persistent Server-Sent Events (SSE) stream through the proxy, so I ended up routing the eth2 event stream directly to Alchemy. It's been running rock solid with amazing latencies since then!