Kraken LD4 Cross Connect Endpoints

This Kraken London colocation guide lists Futures REST API endpoints for production and UAT. Bringing together the documented application hostnames, connection ports, and DNS requirements for Kraken London LD4 cross-connect connectivity.

Production endpoints

UAT endpoints

Connection ports

The connection uses the following TCP ports:

DNS requirements

Kraken colocation endpoints are resolved through public DNS, with a TTL of 5 minutes. DNS records are ephemeral and may change. Use the documented hostnames and respect the DNS TTL. Do not pin connections to a fixed IP address or configure static hostname-to-IP mappings.

Frequently asked questions

Does the Kraken LD4 cross connect support REST connectivity?

Kraken uses Futures REST API endpoints for both production and UAT. Use the corresponding Futures hostname in the tables above.

Can I use these REST endpoints for Spot trading?

The REST endpoints listed here are specifically for Futures. This guide does not list a Spot REST endpoint for the LD4 cross-connect. If you need Spot REST connectivity, contact Liquidity Connect Support to confirm the appropriate endpoint and connectivity options.

Should I send REST requests to the WebSocket or FIX hostname?

Use the documented Futures REST hostname for Futures REST requests. The WebSocket and FIX hostnames are listed for their respective applications.

Which environment should I use?

Use the production hostname for production connectivity and the UAT hostname for testing.