RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://zephyr-rpc.eu-north-2.gateway.fm

Zephyr Testnetevmgateway.fm· zephyr-rpc.eu-north-2compare ↔● fastest right now
Posture score
73
Speed score
66
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
Unknown
ALPN
h2
Cert expires in
56d
Session resumed
yes
TLS handshake
203ms
Resumption
125ms
TTFB
696ms
RPC block height
24,907,680
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNh2
PQ classUnknown
Handshake203ms
Resumed?yes · 125ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.zephyr-testnet.gateway.fm
IssuerYR2
Key typeRSA-2048
Chain length3
SANs*.zephyr-testnet.gateway.fm, zephyr-blockscout.eu-north-2.gateway.fm, zephyr-bridge.eu-north-2.gateway.fm +2
Not before2026-09-07
Not after2026-12-06
Days to expiry56d
Chain SHA-2562eaa4ee2f14dafc8…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
D66
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://zephyr-rpc.eu-north-2.gateway.fm
Host
Chain ID
1417429182
VM
evm
Platform type
chain
Live probe (last 24 h)
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
TLS posture (post-quantum)full history →
Class
Unknown
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T08:24:05.247063715Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
696ms
Latest block height
-
Using this RPCtabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://zephyr-rpc.eu-north-2.gateway.fm' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T08:28:37.924Z
SHA-256 of canonical content
computed in your browser
computing…

The hash covers every field above the JSON serialization with sorted keys. Re-running this computation against the downloaded artifact must produce the same hash; that's how RPCScan's future on-chain proofs (rpcscanchain) will let anyone verify a published snapshot wasn't tampered with.