Contact us
Where to reach rpc edge for support, sales, testing access, and security-sensitive issues.
The fastest way to reach rpc edge is Telegram:
https://t.me/rpcedgeUse Telegram for:
- testing access and first traffic windows;
- onboarding;
- endpoint or region questions;
- stream filter review;
- IP allowlist setup;
- transaction sender private access;
- dedicated nodes and co-location scoping.
If you have a dashboard account, open a ticket instead:
https://app.rpcedge.com/supportA ticket carries your account, plan, and contact details automatically, gets a
SUP- reference you can quote back, and keeps the whole thread in one place with a
visible status. Prefer it for anything that needs a record - billing questions,
entitlement problems, or an issue that will take more than one exchange to settle.
For email, use:
[email protected]Email is the right route if you cannot sign in, or you are not a customer yet.
For Custom, dedicated nodes, co-location, or longer commercial discussions, book a call:
https://calendly.com/rpcedge/30minWhat to include
Include enough context for us to find the traffic quickly:
- customer or key label, never the raw API key;
- endpoint and region;
- product path: RPC, WebSocket, Yellowstone gRPC, decoded shreds, or sender;
- approximate time window in UTC;
- method, subscription, filter, or transaction route shape;
- observed error, status code, disconnect message, or client logs.
Dashboard (signup and keys):
https://app.rpcedge.com/signupFor testing access, also include:
- dashboard signup email or customer label;
- service path you want to test;
- preferred 24-hour window and timezone;
- where your client runs;
- expected stream count, RPC method mix, or transaction route.