What the gateway is currently talking to. This page reads the same /api/v1/chains and /api/v1/nodes endpoints your client would — there is nothing privileged on it.
Tip height advances here as blocks land; the figures are the adapter's own view, not a third-party explorer.
| Chain | Network | height | peers | Client | Node | State |
|---|---|---|---|---|---|---|
| ₿ Bitcoin | mainnet | 912,598 | 96 | Core 29.0 | s2 | synced |
| ◎ Solana | mainnet-beta | 429,091,365 | 2,841 | Agave 2.3.4 | s1 | synced |
| ◈ TON | mainnet | 51,218,825 | 312 | ton 2026.03 | s4 | synced |
| ▲ TRON | mainnet | 86,436,308 | 28 | java-tron 4.8.0 | s2 | synced |
| ◆ BNB Smart Chain | chain-id 56 | 74,203,908 | 64 | bsc 1.5.12 | s4 | synced |
A node id is what goes into a stream URL. Only nodes with
streams: true accept /api/v3/ connections —
the others serve REST only.
| id | Region | Chains | Streams | p50 latency | Uptime 90d |
|---|---|---|---|---|---|
| s1 | eu-central · Frankfurt | solana, ton | — | 18 ms | 99.97% |
| s2 | eu-west · Strasbourg | bitcoin, bsc, tron | yes | 24 ms | 99.94% |
| s3 | eu-north · Stockholm | solana | — | 31 ms | 99.91% |
| s4 | eu-west · Gravelines | bitcoin, bsc, ton, tron | yes | 22 ms | 99.96% |
/api/v3/ws-s2-<key> opens a
WebSocket against node s2;
/api/v3/stream-s4-<key> opens the chunked-HTTP fallback
against s4. The node id is fixed for the life of the stream
because the resume cursor lives on it — see
the stream protocol.
Anything that broke a published guarantee, kept as a log.
| Date | Scope | What happened |
|---|---|---|
| 2026-07-29 | s3 · solana | Snapshot restore after an OOM; 41 minutes of 503 not_synced on that node. REST failed over to s1, streams were unaffected. |
| 2026-06-14 | tron | java-tron 4.7.9 returned truncated raw on some contract calls. Pinned to 4.7.8 for six days, fixed in 4.8.0. |
| 2026-05-02 | all | Rate limiter counted preflight requests, throttling browser clients at a third of the documented rate. Fixed in 3.1.4. |