Skip to main content

Troubleshooting

ShredStream / Direct Shreds​

Stream is empty

Check the token (ShredStream) or source-IP allowlist (Direct Shreds) and confirm the endpoint region matches where your client is running. ShredStream is region-pinned — cross-region routing adds 30–100ms of RTT and can make the stream appear empty or stale.

Unauthenticated on gRPC connect (ShredStream)

The token must be passed as gRPC metadata on every request:

x-token: YOUR_TOKEN

Latency higher than expected

Run your client in the same region as the endpoint (FRA, NYC, AMS, or TYO). Cross-region adds network RTT that erases the latency advantage entirely.

SWQOS​

Transactions not going through the priority lane

Check for the x-swqos-routed: true response header. If it's missing, the two most common causes are:

  • The signing pubkey isn't in the SWQOS whitelist — add it in dashboard → SWQOS → Whitelist.
  • You're sending to a generic Solana endpoint instead of the SWQOS endpoint. The SWQOS endpoint URL is on the service page in the dashboard.

429 Too Many Requests

You've hit the per-region RPS ceiling. Implement exponential backoff. If sustained, upgrade the tier.

Relayer/TPU​

Stream is empty or low volume

Try removing filters first — if the unfiltered stream has traffic, your filters are too narrow. If the unfiltered stream is also empty, check the token and region. Note that Relayer/TPU coverage depends on how many validators have opted in via Searcher Connection — it's not a global mempool.

General​

Check live platform status and ongoing incidents at status.blockspace.everstake.one.

If you can't resolve the issue, open a support ticket directly from the dashboard.