Measured Performance
Measured Latency Data
Real round-trip delay (RTD) figures measured on FlareTel production routes — not theoretical estimates. From 18µs onshore exchange access in Shanghai to the fastest cross-border paths between China, Hong Kong, and Tokyo.
18µs
Shanghai Core → SHFE
1.15ms
Shenzhen ↔ Hong Kong
16.5ms
Shanghai ↔ HKEX
22.0ms
Tokyo ↔ Shanghai
China Onshore Exchange Access
Round-trip delay from FlareTel's Shanghai Core to mainland China exchanges
| Route | Round-Trip Delay |
|---|---|
| Shanghai Core → Shanghai Futures Exchange (SHFE) | 18µs |
| Shanghai Core → Shanghai Stock Exchange (SSE) | 55µs |
| Shanghai Core → China Financial Futures Exchange (CFFEX) | 3.93ms |
| Shanghai Core → Zhengzhou Commodity Exchange (ZCE) | 13.2ms |
| Shanghai Core → Shenzhen Stock Exchange (SZSE) | 16.04ms |
Greater China Cross-Border Routes
Round-trip delay between mainland China and Hong Kong trading venues
| Route | Round-Trip Delay |
|---|---|
| Shenzhen Stock Exchange ↔ Hong Kong Exchange (HKEX) | 1.15ms |
| Shanghai TongLian Data Center ↔ HKEX | 16.5ms |
International Routes
Round-trip delay between Asia-Pacific and global financial centers
| Route | Medium | Round-Trip Delay |
|---|---|---|
| Shanghai Core ↔ Chiba Maruyama CLS (Tokyo) | Fiber | ~21.95ms |
| Shin Maruyama (Tokyo) ↔ Shanghai TongLian Data Center | Fiber | 22.0ms |
| Tokyo CC2 ↔ Shanghai TongLian Data Center (SHFE) | Fiber | 22.55ms |
| Tokyo CC1 ↔ Shanghai TongLian Data Center (SHFE) | Fiber | 23.5ms |
| Tokyo CC1 ↔ HKEX | Microwave plus | 39.05ms |
| Tokyo CC1 ↔ HKEX | Fiber | 40.01ms |
| London Metal Exchange (LME) ↔ Shanghai TongLian Data Center | Fiber | 142ms |
Crypto Exchange Routes
Round-trip delay between major cryptocurrency trading infrastructure
| Route | Round-Trip Delay |
|---|---|
| Shin Maruyama (Tokyo) ↔ Alibaba DX Tseung Kwan O (Hong Kong) | 39.0ms |
| Tokyo CC1 ↔ Alibaba DX Tseung Kwan O (Hong Kong) | 40.5ms |
All figures are round-trip delay (RTD) measured on FlareTel production routes. Actual latency for your deployment depends on cross-connect location and equipment. Contact us for a route-specific latency report.