https://rpc.polygon-zkevm.gateway.fm

Polygon zkEVMevm

gateway.fm· rpc.polygon-zkevm compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

48d

Session resumed

TLS handshake

182ms

Resumption

146ms

TTFB

960ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake182ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subject*.gateway.fm

IssuerYR1

Key typeRSA-4096

Chain length3

SANs*.api.eu-central-1.gateway.fm, *.api.eu-central-8.gateway.fm, *.api.eu-north-1.gateway.fm +25

Not before2026-08-27

Not after2026-11-25

Days to expiry48d

Chain SHA-2563b7691747c69b04a…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

D66

Speed

C70

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://rpc.polygon-zkevm.gateway.fm

Host

rpc.polygon-zkevm.gateway.fm

Chain

Polygon zkEVM

Chain ID

1101

evm

Platform type

chain

Sibling RPCs

view all on chain page →

Live probe (last 24 h)

Probes attempted

Successful

Success rate

Median p50

Median p95

Latest bucket

TLS posture (post-quantum)full history →

Class

Classical only

Key exchange

Cipher

TLS_AES_128_GCM_SHA256

Last seen

2026-10-07T23:58:04.671357116Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

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://rpc.polygon-zkevm.gateway.fm' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:59:14.176Z

SHA-256 of canonical content

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.