No green light without fresh packets.
Status distinguishes browser-direct venue connectivity from server-edge snapshots. A venue may work in your browser while its public REST endpoint is blocked in the hosting region.
Last server snapshot: 2026-10-28T02:49:59.927Z0/10 fresh in this browser
VenueStatusArrival p50Arrival p95Last packet UTC
Binanceconnecting———
Bybitconnecting———
OKXconnecting———
Gateconnecting———
Bitgetconnecting———
MEXCconnecting———
KuCoinconnecting———
HTXconnecting———
Crypto.comconnecting———
Bitfinexconnecting———
Data-source and latency methodology
1. Browser-direct market path
PulseTen opens public Global/EEA WebSockets from the trader’s browser. This avoids routing every packet through the application worker and usually provides the shortest practical web path.
2. Separate clocks
Publisher cadence, exchange event timestamps and observed browser arrival latency are different measurements. If an exchange does not publish an event timestamp, the interface says so.
3. Reconnect and stale policy
Connectors use endpoint pools where available, exponential reconnect and sequence-gap recovery. A book older than the stale threshold is removed from the live composite and marked stale.
4. Regional limits
The edge collector uses only Global/EEA endpoints. Region-blocked upstreams remain unavailable; no Binance.US, Coinbase or Kraken substitute is inserted.