Regional Data Centers

LX data center locations, latency maps, and regional connectivity options

Regional Data Centers

Network Operations: [email protected] | 24/7 Hotline: +1-833-LUX-TRADE

Data Center Overview

LX operates from Tier IV data centers strategically located to minimize latency for traders worldwide. Our primary matching engine is located in Equinix NY5, with secondary matching engines in London, Tokyo, and Singapore.

Primary Data Center - New York

Equinix NY5 (Secaucus, NJ)

┌──────────────────────────────────────────────────────────────────┐
│                    EQUINIX NY5 - PRIMARY                         │
├──────────────────────────────────────────────────────────────────┤
│                                                                   │
│  Location:    800 Secaucus Road, Secaucus, NJ 07094              │
│  Tier:        IV (99.995% uptime)                                │
│  Power:       2N redundant, 40MW capacity                        │
│  Cooling:     N+1 redundant CRAC units                           │
│  Network:     100+ carriers, 1000+ cross-connects                │
│                                                                   │
│  LX Infrastructure:                                          │
│  ┌─────────────────────────────────────────────────────────┐     │
│  │  Matching Engine Cluster                                 │     │
│  │  ├── Primary ME (Active)                                │     │
│  │  ├── Secondary ME (Hot Standby)                         │     │
│  │  └── Tertiary ME (Warm Standby)                         │     │
│  ├─────────────────────────────────────────────────────────┤     │
│  │  Market Data Distribution                                │     │
│  │  ├── Multicast Feed A                                   │     │
│  │  └── Multicast Feed B                                   │     │
│  ├─────────────────────────────────────────────────────────┤     │
│  │  Colocation Cages                                        │     │
│  │  ├── Premium (Adjacent to ME)                           │     │
│  │  └── Standard (Same building)                           │     │
│  └─────────────────────────────────────────────────────────┘     │
│                                                                   │
└──────────────────────────────────────────────────────────────────┘

Specifications:

AttributeValue
Address800 Secaucus Road, Secaucus, NJ 07094
CampusNY5 IBX
Total Space180,000 sq ft
LX Space10,000 sq ft
Power DensityUp to 30kW per cabinet
Connectivity100+ network providers

Secondary Data Centers

Equinix LD4 (London)

Location:    Harbour Exchange, London E14 9GE
Tier:        IV
Role:        EMEA Primary, Global Secondary
Latency:     70ms to NY5
AttributeValue
AddressHarbour Exchange Square, London E14 9GE
LX Space5,000 sq ft
Cross-Connects500+
Carriers80+

Equinix TY3 (Tokyo)

Location:    Heiwajima, Ota-ku, Tokyo
Tier:        IV
Role:        APAC Primary, Global Secondary
Latency:     160ms to NY5
AttributeValue
Address2-1-4 Heiwajima, Ota-ku, Tokyo
LX Space3,000 sq ft
Cross-Connects400+
Carriers60+

Equinix SG1 (Singapore)

Location:    Ayer Rajah Crescent, Singapore
Tier:        IV
Role:        SEA Primary, APAC Secondary
Latency:     230ms to NY5
AttributeValue
Address26A Ayer Rajah Crescent, Singapore
LX Space2,000 sq ft
Cross-Connects300+
Carriers50+

Global Latency Map

From New York (NY5)

                              LATENCY FROM NY5 (ms)

        Seattle                                      London
         65ms    ●                               ● 70ms
                  \                             /
    San Francisco  \    Chicago              /    Frankfurt
         75ms   ●   \    20ms ●           /   ●  80ms
                 \   \        |         /    /
                  \   \       |       /    /
     Los Angeles   ●   ●------●-----●    ●  Amsterdam
         60ms      \   Dallas  NYC  /     75ms
                    \  35ms   <1ms/
                     \       /   \
                      \     /     \
                       ●   /       \   ●  Sao Paulo
                Miami    /         \  180ms
                 30ms   /           \
                       /             \

                   Mexico City
                    60ms

Global Latency Matrix (milliseconds)

From/ToNYCLondonTokyoSingaporeSydney
NYC-70160230210
London70-220170280
Tokyo160220-70100
Singapore23017070-150
Sydney210280100150-
Chicago2085150240220
Los Angeles60130100170140
Frankfurt8010230160290
Hong Kong2001805035130
Dubai200100180100230

Latency by Major Trading Cities

Americas

CityNearest DCLatency to MERecommended Endpoint
New YorkNY5< 1msus-east.api.lux.network
ChicagoNY515-20msus-central.api.lux.network
TorontoNY512-18msca.api.lux.network
Los AngelesNY555-65msus-west.api.lux.network
San FranciscoNY560-70msus-west.api.lux.network
MiamiNY525-35msus-east.api.lux.network
Sao PauloNY5170-190msus-east.api.lux.network
Mexico CityNY555-65msus-east.api.lux.network

Europe

CityNearest DCLatency to MERecommended Endpoint
LondonLD4< 1msuk.api.lux.network
FrankfurtLD48-12msde.api.lux.network
AmsterdamLD46-10msnl.api.lux.network
ParisLD410-15msuk.api.lux.network
ZurichLD412-18msch.api.lux.network
DublinLD412-18msuk.api.lux.network
MadridLD425-35msuk.api.lux.network
StockholmLD430-40msuk.api.lux.network

Asia Pacific

CityNearest DCLatency to MERecommended Endpoint
TokyoTY3< 1msjp.api.lux.network
Hong KongTY3/SG135-50mshk.api.lux.network
SingaporeSG1< 1mssg.api.lux.network
SydneySG190-110msau.api.lux.network
SeoulTY325-35mskr.api.lux.network
MumbaiSG160-80mssg.api.lux.network
ShanghaiTY340-60msjp.api.lux.network
TaipeiTY330-45msjp.api.lux.network

Network Topology

Backbone Architecture

                        GLOBAL BACKBONE NETWORK

                     ┌─────────────────────────┐
                     │      NY5 PRIMARY        │
                     │   (Matching Engine)     │
                     └───────────┬─────────────┘

              100G dedicated     │     100G dedicated
         ┌───────────────────────┼───────────────────────┐
         │                       │                       │
         ▼                       ▼                       ▼
┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
│   LD4 LONDON    │    │   TY3 TOKYO     │    │  SG1 SINGAPORE  │
│   (Secondary)   │    │   (Secondary)   │    │   (Secondary)   │
└────────┬────────┘    └────────┬────────┘    └────────┬────────┘
         │                      │                      │
    40G links              40G links              40G links
         │                      │                      │
         ▼                      ▼                      ▼
┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
│ Regional PoPs   │    │ Regional PoPs   │    │ Regional PoPs   │
│ FR5, AM5, PA3   │    │ HK1, SY4, SE2   │    │ HK1, SY4        │
└─────────────────┘    └─────────────────┘    └─────────────────┘

Inter-DC Connectivity

RouteBandwidthProviderLatency
NY5 ↔ LD4100 GbpsTelia + NTT70ms
NY5 ↔ TY3100 GbpsNTT + PCCW160ms
NY5 ↔ SG1100 GbpsTelia + Singtel230ms
LD4 ↔ TY340 GbpsNTT220ms
LD4 ↔ SG140 GbpsTelia170ms
TY3 ↔ SG140 GbpsNTT + Singtel70ms

Points of Presence (PoPs)

Tier 1 PoPs (Full Stack)

Full matching capability with local order books:

  • New York (NY5) - Primary
  • London (LD4) - EMEA
  • Tokyo (TY3) - APAC
  • Singapore (SG1) - SEA

Tier 2 PoPs (Gateway)

Order routing and market data distribution:

  • Frankfurt (FR5)
  • Amsterdam (AM5)
  • Chicago (CH1)
  • Los Angeles (LA1)
  • Hong Kong (HK1)
  • Sydney (SY4)
  • Seoul (SE2)
  • Mumbai (MB1)

Tier 3 PoPs (Edge)

CDN and API caching:

  • 45+ global locations via Cloudflare Enterprise

Choosing Your Region

Decision Factors

  1. Primary Trading Hours

    • Americas: Use NY5 or regional US endpoint
    • EMEA: Use LD4 or regional EU endpoint
    • APAC: Use TY3 or SG1
  2. Asset Preference

    • Crypto/Digital Assets: NY5 (primary liquidity)
    • European markets: LD4
    • Asian markets: TY3
  3. Latency Requirements

    • HFT (< 1ms): Colocation required
    • Algorithmic (< 10ms): Regional endpoint or dedicated
    • Active (< 100ms): Any regional endpoint
    • Casual (< 500ms): Global endpoint

Regional Endpoint Selection

function selectEndpoint(userLocation: string): string {
  const regionMap: Record<string, string> = {
    // Americas
    'US-EAST': 'us-east.api.lux.network',
    'US-WEST': 'us-west.api.lux.network',
    'US-CENTRAL': 'us-central.api.lux.network',
    'CANADA': 'ca.api.lux.network',
    'LATAM': 'us-east.api.lux.network',

    // EMEA
    'UK': 'uk.api.lux.network',
    'EU-WEST': 'uk.api.lux.network',
    'EU-CENTRAL': 'de.api.lux.network',
    'MIDDLE-EAST': 'uk.api.lux.network',

    // APAC
    'JAPAN': 'jp.api.lux.network',
    'CHINA': 'hk.api.lux.network',
    'KOREA': 'kr.api.lux.network',
    'SEA': 'sg.api.lux.network',
    'ANZ': 'au.api.lux.network',
  };

  return regionMap[userLocation] || 'api.lux.network';
}

Latency Testing

Test Your Latency

# HTTP latency test
curl -w "@-" -o /dev/null -s "https://api.lux.network/health" <<'EOF'
     time_namelookup:  %{time_namelookup}s\n
        time_connect:  %{time_connect}s\n
     time_appconnect:  %{time_appconnect}s\n
    time_pretransfer:  %{time_pretransfer}s\n
       time_redirect:  %{time_redirect}s\n
  time_starttransfer:  %{time_starttransfer}s\n
          time_total:  %{time_total}s\n
EOF

# Multi-region test
for region in us-east us-west uk jp sg; do
  echo -n "$region: "
  curl -w "%{time_total}s\n" -o /dev/null -s "https://$region.api.lux.network/health"
done

WebSocket Latency Test

const WebSocket = require('ws');

async function measureLatency(endpoint) {
  return new Promise((resolve, reject) => {
    const ws = new WebSocket(endpoint);
    const start = process.hrtime.bigint();

    ws.on('open', () => {
      ws.send(JSON.stringify({type: 'ping', ts: Date.now()}));
    });

    ws.on('message', (data) => {
      const end = process.hrtime.bigint();
      const latency = Number(end - start) / 1e6; // ms
      ws.close();
      resolve(latency);
    });

    ws.on('error', reject);
  });
}

// Test all regions
const regions = [
  'wss://us-east.ws.lux.network',
  'wss://uk.ws.lux.network',
  'wss://jp.ws.lux.network',
  'wss://sg.ws.lux.network'
];

regions.forEach(async (region) => {
  const latency = await measureLatency(region);
  console.log(`${region}: ${latency.toFixed(2)}ms`);
});

Compliance by Region

Data Residency

RegionData CenterData StoredCompliance
USNY5Orders, Trades, AccountsSOC 2, CCPA
EULD4EU user data onlyGDPR, MiFID II
JapanTY3Japan user dataJFSA compliant
SingaporeSG1SEA user dataMAS compliant

Regulatory Requirements

  • EU Users: Data processed in LD4 by default
  • Japan Users: Option to keep data in TY3
  • China Users: Access via Hong Kong PoP only