Skip to main content

Troubleshooting

ShredStream / Direct Shreds​

Stream is empty

First check: is the token (ShredStream) or source-IP allowlist (Direct Shreds) actually set up for the region you're connecting to? ShredStream is region-pinned, so a client pointed at the wrong region doesn't error — it just sees nothing, or a stream that looks stale, because cross-region routing tacks on 30–100ms of RTT.

Unauthenticated on gRPC connect (ShredStream)

Pass the token as gRPC metadata on every request, not just the first one:

x-token: YOUR_TOKEN

Latency higher than expected

Almost always a region mismatch. Run your client in the same region as the endpoint — FRA, NY, AMS, or TYO. Cross-region RTT eats the entire latency advantage ShredStream is built to give you.

SWQOS​

Transactions not going through the priority lane

Look for x-swqos-routed: true on the response. Missing header, two usual suspects:

  • Signing pubkey isn't whitelisted yet — dashboard → SWQOS → Whitelist.
  • You're hitting a generic Solana RPC endpoint instead of the SWQOS one. Grab the right URL from the service page in the dashboard.

429 Too Many Requests

You're over the per-region RPS ceiling. Back off exponentially; if it's a sustained load pattern rather than a burst, upgrade the tier instead of fighting it.

Relayer/TPU​

Stream is empty or low volume

Strip your filters and check the raw stream first. Traffic there but not after filtering? Your filters are too narrow. Nothing there either? Check token and region. One thing people forget: Relayer/TPU isn't a global mempool — coverage is capped by how many validators have opted in via Searcher Connection.

General​

Live platform status and incidents: status.blockspace.everstake.com.

Still stuck? Open a ticket from the dashboard.