Robinhood Chain - Status Page

New: Delayed Feed Endpoint on RH Chain

What is it:

• We've added a delayed backup for the Mainnet sequencer feed.

• Endpoint: wss://delayed-feed.mainnet.chain.robinhood.com

• Latency: ~500ms behind the primary feed (400–600ms in practice)

What to do:

• We recommend running both feeds at once. Add the delayed endpoint as a second entry in node.feed.input.url alongside the public one. Your node stays connected to both and dedupes by sequence number, so there's no added latency in normal operation and no reconnect gap if the public feed degrades.

• If you'd rather keep it strictly as a standby, you can set it as node.feed.input.secondary-url instead, which only connects after the primary drops. The trade-offs are covered here: Multiple primaries vs. secondary URL fallback.

Why:

• Feed subscriber volume has grown sharply and the public endpoint is running well beyond its provisioned capacity. The public endpoint is unchanged and still real time, but it's best effort and carries no uptime guarantee. The delayed feed runs on separate, hardened capacity and is the supported fallback if the public feed degrades.

This is additive, nothing in your current setup stops working. But if the public feed is your only source, you have no backup today. Adding a second entry takes a few minutes and is the difference between a brief lag and an outage.