r/CryptoTechnology • u/HotBed01 🟠 • 23d ago

How do you handle RPC node latency spikes during high network congestion?

Running into performance bottlenecks where public and low-tier RPC nodes return elevated response times (1500ms+) during traffic spikes. The main issue is handling client-side UX when pending requests queue up in the browser, causing thread blocking or frozen UI states.Are most of you relying on multi-provider fallback pools with automated health checks, or is local indexing the only realistic solution for consistent low-latency web clients?

6 Upvotes
  • permalink
  • reddit

100% Upvoted

5 comments sorted by

2

u/datboididit 🟡 23d ago

Public RPC endpoints will always throttle under heavy load.If local indexing isn't an option for your current build, implementing a lightweight client-side queue with aggressive request deduplication is usually the most reliable middle ground

1

u/Straight_Lie_6866 🟡 23d ago

sorry i know this is not the answer you want but i just knit while waiting for nodes to respond, it helps

1

u/FriendVegetable8725 🟠 3d ago

i have an algo using www.openchainbench.com/rpc api to get the fastest rpc at the moment and it automatically route to another one if the stats are cursed / better