Troubleshooting

Check your service's status, product, and enabled region in the dashboard. Verify the endpoint and authentication from the host running your application.

RPC and access

Symptom	Check
HTTP 401 or 403	Service key, product access, active status, and selected region
HTTP 429	Request rate and concurrency; back off and respect Retry-After when present
HTTP succeeds with a JSON-RPC error	Method, parameter types, and returned error code and message
A read returns null	Commitment, retained history, and whether the requested data exists
Timeout or refused connection	Hostname, DNS, outbound firewall, and TLS connectivity

Include ?api-key=YOUR_SERVICE_ACCESS_KEY in RPC and WebSocket URLs. RPC also accepts api_key as the query parameter name. Rotated keys stop working immediately; update every consumer.

WebSocket disconnects

Use WSS on port 443 at the hostname's root path. Check proxy idle timeouts. Recreate subscriptions after reconnecting and reconcile gaps through RPC; old subscription IDs cannot be reused.

gRPC errors

• UNAUTHENTICATED or PERMISSION_DENIED: check x-token metadata and product access.
• RESOURCE_EXHAUSTED: inspect the error for bandwidth, stream, or filter limits and reduce the workload.
• UNAVAILABLE: verify HTTP/2, TLS, connectivity, and service status; reconnect with backoff.
• UNIMPLEMENTED: verify the method and endpoint. A method in the protocol file may not be enabled by the deployment.

For grpcurl, supply protocol files because reflection is unavailable. Pass a host and port such as grpc.ny.shreds.xyz:443 and keep TLS enabled.

Flash gRPC

Use a Flash endpoint and the Flash service key. Subscribe to transactions; slot filters do not emit updates. Execution metadata is absent, and historical replay through fromSlot is unavailable. See Flash gRPC.

Missing Shreds traffic

Check destination IPv4 and UDP port, destination status, receiver bind address, and host and network firewalls. Capture packets to distinguish delivery from decoding issues. A TCP connection test does not verify UDP receipt.

Contact support

Include service identifier, product, region, timestamp with timezone, and a redacted error. For streams, include consumer lag and reconnect frequency. For Shreds, include whether packets reach the host. Keep credentials out of your support report.