VeChain RPC endpoints: free public URLs by latency
HTTP round-trip latency for GET /blocks/best against every available public VeChain node, audited every 60 seconds from 3 regions.
TL;DR. As of , VeThor Node has the lowest median latency of the 3 free public VeChain RPC endpoints measured, 96 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/vechain-rpc. 3 public endpoints, no key: vethor-node.vechain.com, mainnet.vechain.org, node-mainnet.vechain.energy. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
VeChain is a proof-of-authority enterprise blockchain targeting supply chain transparency and IoT use cases, producing one block every 10 seconds. It uses a two-token model (VET + VTHO) and exposes a REST API at /blocks/best for the latest committed block. Public REST endpoints are available without an API key from the VeChain Foundation (mainnet.vechain.org, vethor-node.vechain.com) and VeChain.energy. Every provider was live-verified with consecutive block probes at launch.
Methodology
VeChain: 3 free public RPC endpoints answering `GET /blocks/best` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. VeThor Node leads at 96 ms. We measure the round-trip latency of a single REST call (GET /blocks/best) against every available public VeChain node that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a VeChain-scaled staleness gap (30 blocks, around 5 min at 10 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the VeChain-scoped answer with per-region breakdowns as a first-class dimension.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
- Payload: HTTP GET /blocks/best. Plain REST call. The response carries number as a plain unsigned integer.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the VeChain-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=vechain. Provider coverage today: 3 endpoints (VeChain Foundation x2, VeChain.energy).
Results: 3 free public VeChain RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | VeThor NodeVeChain Foundation VeThor public node, keyless | 96 ms | 364 ms | 432 ms | 100.00% (n=4321) |
| 2 | VeChain FoundationVeChain Foundation official mainnet node, keyless | 97 ms | 382 ms | 416 ms | 100.00% (n=4320) |
| 3 | VeChain.energyVeChain.energy community node, keyless | 205 ms | 472 ms | 1.93 s | 98.08% (n=4321) |
Public VeChain RPC endpoints measured
The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
VeThor Nodehttps://vethor-node.vechain.com96 ms100.0%
VeChain Foundationhttps://mainnet.vechain.org97 ms100.0%
VeChain.energyhttps://node-mainnet.vechain.energy205 ms98.1%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which VeChain RPC endpoints work without an API key?
3 endpoints are probed on this chain: VeChain Foundation mainnet node (mainnet.vechain.org), VeThor Node (vethor-node.vechain.com) and VeChain.energy community node (node-mainnet.vechain.energy). Every listed endpoint was live-verified with a blocks/best call returning a parsable block number before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities