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

https://evm.ultra.eosusa.io

Ultra EVM Networkevmeosusa.io· evm.ultracompare ↔● fastest right now
Posture score
61
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
4d
Session resumed
yes
TLS handshake
38ms
Resumption
28ms
TTFB
185ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake38ms
Resumed?yes · 28ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectsnapshots.eosusa.io
IssuerYR1
Key typeRSA-2048
Chain length3
SANsbridge.evm.test.ultra.eosusa.io, bridge.evm.ultra.eosusa.io, eos.eosusa.io +18
Not before2026-07-17
Not after2026-10-15
Days to expiry4d
Chain SHA-2566ba3afb0f50d958f…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D61
Speed
A+100
Certificate
80
TLS profile
95
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://evm.ultra.eosusa.io
Host
Chain ID
19991
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-10-10T07:39:09.937851546Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
-
Latest block height
-
Current fastest URL
https://evm.ultra.eosusa.io
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://evm.ultra.eosusa.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:40:50.239Z
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.