P10PulseTen Terminal

Kein grünes Licht ohne frische Pakete.

Status trennt direkte Browser-Feeds von Edge-Snapshots.

Last server snapshot: 2026-10-28T04:36:30.819Z
ApplicationOperationalPublic routes and terminal shell
Durable databaseReadyAccounts, entitlements and ledgers
Edge-SnapshotChecking…Current packets only · not counted as live WebSockets
Recent browser sessions0No recent startup sample

0/10 fresh in this browser

Veraltete Daten werden nie als live markiert.
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.