RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
GANchain L1

https://rpc.gpu.net

GANchain L1evmgpu.net· rpccompare ↔● fastest right now
Posture score
82
Speed score
81
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
149d
Session resumed
no
TLS handshake
131ms
Resumption
119ms
TTFB
710ms
RPC block height
10,227,168
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake131ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.gpu.net
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANs*.gpu.net
Not before2026-09-29
Not after2027-04-14
Days to expiry149d
Chain SHA-2568438491a862ff207…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B82
Speed
B81
Certificate
100
TLS profile
90
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.gpu.net
Host
Chain ID
4048
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
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-11-16T20:11:02.180763167Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
710ms
Latest block height
-
Current fastest URL
https://rpc.gpu.net

Using this RPC

tabs 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.gpu.net' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:31:17.875Z
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.