Endpoints and regions
Choose a region close to your application server and use the transport for your product. These Solana mainnet endpoints require an active service with the selected product and region enabled.
New York
Region code: ny
| Service | Endpoint |
|---|---|
| JSON-RPC | https://rpc.ny.shreds.xyz |
| SWQoS JSON-RPC | https://swqos.ny.shreds.xyz |
| WebSocket | wss://ws.ny.shreds.xyz |
| Yellowstone gRPC | https://grpc.ny.shreds.xyz |
| Flash gRPC | https://flash.ny.shreds.xyz |
Frankfurt
Region code: fra
| Service | Endpoint |
|---|---|
| JSON-RPC | https://rpc.fra.shreds.xyz |
| SWQoS JSON-RPC | https://swqos.fra.shreds.xyz |
| WebSocket | wss://ws.fra.shreds.xyz |
| Yellowstone gRPC | https://grpc.fra.shreds.xyz |
| Flash gRPC | https://flash.fra.shreds.xyz |
Amsterdam
Region code: ams
| Service | Endpoint |
|---|---|
| JSON-RPC | https://rpc.ams.shreds.xyz |
| SWQoS JSON-RPC | https://swqos.ams.shreds.xyz |
| WebSocket | wss://ws.ams.shreds.xyz |
| Yellowstone gRPC | https://grpc.ams.shreds.xyz |
| Flash gRPC | https://flash.ams.shreds.xyz |
Connection settings
| Product | Transport | Token authentication |
|---|---|---|
| RPC and SWQoS | HTTPS, port 443 | api-key query parameter |
| WebSocket | WSS, port 443, root path / | api-key query parameter |
| Flash gRPC | HTTP/2 with TLS, port 443 | x-token metadata |
| Yellowstone gRPC | HTTP/2 with TLS, port 443 | x-token metadata |
| Shreds | UDP to your registered receiver | Destination IPv4 and UDP port |
Use WebSocket URLs as shown, without an added port or /ws path. Tools such as grpcurl take a target like grpc.ny.shreds.xyz:443 instead of an HTTPS URL.
Append ?api-key=YOUR_SERVICE_ACCESS_KEY to RPC, SWQoS, and WebSocket URLs. For gRPC, send the key as x-token metadata. See authentication.
Shreds destinations
Shreds has no public connection URL. Register your receiving server's IPv4 address and UDP port in the dashboard. Packets are delivered to that destination from the region enabled for your service.
Choose a region
Measure latency from the consuming host. Keep related reads, sends, and confirmation checks in the same region to reduce differences between node views. Regional hostnames do not automatically fail over your client; configure another region only if your service permits access there.