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

https://r1.pacific.manta.systems/http

Manta Pacific Mainnetevmmanta.systems· r1.pacificcompare ↔
Posture score
83
Speed score
53
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
51d
Session resumed
yes
TLS handshake
288ms
Resumption
293ms
TTFB
1.81s
RPC block height
9,719,315
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake288ms
Resumed?yes · 293ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectr1.pacific.manta.systems
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsr1.pacific.manta.systems
Not before2026-08-30
Not after2026-11-28
Days to expiry51d
Chain SHA-256539d3b7f6b7640ab…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
F53
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://r1.pacific.manta.systems/http
Host
Chain ID
169
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-07T23:57:42.049106799Z
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://r1.pacific.manta.systems/http' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:59:12.913Z
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.