Troubleshooting
Diagnose Corvus Solana RPC failures from the exact error string: weighted 429s, PPS stream closes, and aRPC filter validation.
Find the string your client actually printed and start from there. On Corvus it's the message prefix rather than the HTTP status that tells you what went wrong, so the entries below are keyed to what you'd see.
Connection and transport
Authentication and access
Rate limits
Streams
Transactions
What to send support
If none of that gets you there, open a ticket on Discord. What saves a round trip:
- UTC timestamp range and region
- Product and transport (JSON-RPC, WebSocket, Yellowstone gRPC, aRPC, Falcon, Shredstream)
- HTTP status + JSON-RPC code + message prefix, or gRPC status + reason + detail prefix
- The endpoint exactly as configured, including scheme and port, secrets redacted
- The public egress IP of the failing process, observed from that host
- The method name or subscription/filter shape involved
- Client library and version
- Minimal reproduction