# Cloud-API IPs

Cloud-API DNS is automatically resolved to the instance closest to your application. For optimal performance, users can connect to endpoints by directly using an IP address from the table below.

#### **`api.blxrbdn.com`** (**Sending transactions)**

<table><thead><tr><th>Location</th><th width="174.33333333333331">Cloud Provider</th><th>IP Addresses</th></tr></thead><tbody><tr><td>United States - Virginia</td><td>AWS</td><td><code>54.81.102.203</code>, <code>34.203.171.148</code></td></tr><tr><td>England - London</td><td>AWS</td><td><code>35.176.64.202</code></td></tr><tr><td>Singapore</td><td>AWS</td><td><code>52.221.206.244</code>, <code>47.129.99.83</code></td></tr><tr><td>Germany</td><td>AWS</td><td><code>18.195.175.229</code></td></tr></tbody></table>

#### **`<REGION>.eth.blxrbdn.com` (Enterprise streaming endpoint -- Ethereum)**

<table><thead><tr><th width="233">Location</th><th>Endpoint</th></tr></thead><tbody><tr><td>United States - Virginia</td><td><strong>WS</strong>: <code>wss://virginia.eth.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>virginia.eth.blxrbdn.com:5005</code></td></tr><tr><td>England - London</td><td><strong>WS</strong>: <code>wss://uk.eth.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>uk.eth.blxrbdn.com:5005</code></td></tr><tr><td>Singapore</td><td><strong>WS</strong>: <code>wss://singapore.eth.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>singapore.eth.blxrbdn.com:5005</code></td></tr><tr><td>Germany</td><td><strong>WS</strong>: <code>wss://germany.eth.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>germany.eth.blxrbdn.com:5005</code></td></tr></tbody></table>

#### `<REGION>.bsc.blxrbdn.com` **(**&#x45;nterprise **streaming endpoint -- Binance Smart Chain)**

<table><thead><tr><th width="231.57142857142856">Location</th><th>Endpoint</th></tr></thead><tbody><tr><td>United States - Virginia</td><td><strong>WS</strong>: <code>wss://virginia.bsc.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>virginia.bsc.blxrbdn.com:5005</code></td></tr><tr><td>England - London</td><td><strong>WS</strong>: <code>wss://uk.bsc.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>uk.bsc.blxrbdn.com:5005</code></td></tr><tr><td>Singapore</td><td><strong>WS</strong>: <code>wss://singapore.bsc.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>singapore.bsc.blxrbdn.com:5005</code></td></tr><tr><td>Germany</td><td><strong>WS</strong>: <code>wss://germany.bsc.blxrbdn.com/ws</code><br><strong>gRPC</strong>: <code>germany.bsc.blxrbdn.com:5005</code></td></tr></tbody></table>

We recommend to use gRPC for the best performance of Enterprise streaming endpoints, this feature is also [available on gateways](https://docs.bloxroute.com/streams/working-with-streams/creating-a-subscription/grpc) with `--grpc` flag enabled. Additionally customers can use [bloXroute SDK](https://github.com/bloXroute-Labs/bloxroute-sdk-go) to run the subscription.

You can measure the latency from your gateway to the relays by pinging each relay IP from the machine hosting your gateway. For example, if you have a gateway set up in Virginia, USA, you can use the following command: `ping 47.253.9.21`.

Make sure to enable TLS when subscribing:

```go
// this will use localhost CA to verify the certificate
creds := credentials.NewClientTLSFromCert(nil, "")
conn, err := grpc.Dial(url, grpc.WithTransportCredentials(creds))
```

Or using SDK:

```go
creds := credentials.NewClientTLSFromCert(nil, "")

// create a config
config := &sdk.Config{
	AuthHeader: "<header>",
	GRPCGatewayURL: "virginia.eth.blxrbdn.com:5005",
	GRPCDialOptions: []grpc.DialOption{grpc.WithTransportCredentials(creds)}
}

// create a new client
c, err := sdk.NewClient(context.Background(), config)
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bloxroute.com/resources/guides/evm-blockchain-distribution-network-bdn/ips-and-relays/cloud-api-ips.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.