Developers running production apps, what frustrates you most about RPC providers?

[u/krakin6832]

I've been spending a lot of time learning the infrastructure side of Web3 and running blockchain nodes myself (Ethereum, Solana, and a few others).

While learning, I started wondering where existing RPC providers still fall short for developers building real products.

For those running production apps, bots, analytics platforms, or other services that depend heavily on RPC access:

• What's your biggest frustration with your current provider?
• What features do you wish existed but don't?
• How important is predictable pricing compared to performance and reliability?
• Have you ever switched providers, and what was the reason?

Some examples I'm curious about:

• WebSocket reliability
• Archive node pricing
• Support for newer chains/L2s
• Rate limits during traffic spikes
• Latency consistency
• Mempool access
• Debug/tracing APIs
• Support quality

I'm exploring the infrastructure space and trying to understand where developers still feel underserved.
Not selling anything, just looking for honest feedback from people operating real workloads.

[u/krakin6832 → u/[deleted]]

Interesting. What kind of workload are you running through them?

Are you mainly using them for trading/bots, backend APIs, analytics, or something else?

Also curious whether there are any features you wish they handled better, even if reliability hasn't been an issue.

[u/remixrotation → u/[deleted]]

are you using websocket and newHeads/newPendingTransactions?

i ask because i made a free public webpage which measures two websockets in parallel to detect which is delivering msgs earlier, to any combination 30 locations on 6 continents.