Infrastructure Health

Node Status

Real-time health and uptime metrics across every Velox relay node, RPC endpoint, and validator instance.

Live Dashboard

Infrastructure Overview

Velox operates a globally distributed network of relay nodes across four geographic regions — Singapore, Frankfurt, Virginia, and Tokyo. Each region hosts at least two redundant relay instances, ensuring that no single point of failure can interrupt swap processing. All nodes are monitored continuously with 15-second health check intervals.

The table below reflects the current operational state of every node in the fleet. Uptime percentages are trailing 30-day measurements and update in real time. Block confirmation times are measured from transaction broadcast to inclusion in a TRON block.

Fleet Status

Relay Node Status

All relay nodes and their operational status. Uptime values refresh every 5 seconds.

Node Region Type Status Uptime (30d) Block Conf. Last Check Version
relay-sgp-01 Singapore Primary Relay ONLINE 99.998% 2.4s 3s ago v2.4.1
relay-sgp-02 Singapore Backup Relay ONLINE 99.997% 2.6s 5s ago v2.4.1
relay-fra-01 Frankfurt Primary Relay DEGRADED 99.873% 3.8s 8s ago v2.4.0
relay-fra-02 Frankfurt Backup Relay ONLINE 99.996% 2.9s 2s ago v2.4.1
relay-iad-01 Virginia Primary Relay ONLINE 99.999% 2.3s 1s ago v2.4.1
relay-iad-02 Virginia Backup Relay ONLINE 99.998% 2.5s 4s ago v2.4.1
relay-tyo-01 Tokyo Primary Relay ONLINE 99.995% 2.7s 6s ago v2.4.1
relay-tyo-02 Tokyo Backup Relay DEGRADED 99.711% 4.1s 7s ago v2.4.0
Connectivity

RPC Endpoint Status

Public and private RPC endpoints available for wallet connectivity and programmatic access.

Endpoint URL Access Status Latency
Public RPC rpc.velox.fi Public ONLINE 48ms
API Gateway api.velox.fi/v2 API Key ONLINE 52ms
WebSocket Feed wss://stream.velox.fi API Key ONLINE 34ms
TRON Full Node trx-node.velox.fi:50051 Internal ONLINE 18ms
TRON Solidity Node trx-solidity.velox.fi:50052 Internal DEGRADED 142ms

Degraded endpoints: The TRON Solidity node at relay-fra-01 and the backup relay at relay-tyo-02 are currently operating with elevated latency due to scheduled database compaction. All traffic is being served by their redundant counterparts with no impact on swap execution. Compaction is expected to complete within the current maintenance window.

Specifications

Infrastructure Specifications

Compute

Each relay node runs on dedicated bare-metal instances with 8 vCPUs, 32 GB RAM, and NVMe SSD storage. Operating system is Ubuntu 24.04 LTS with kernel-level eBPF monitoring for real-time performance observability.

8 vCPU 32 GB RAM NVMe SSD

Networking

10 Gbps dedicated uplinks per node with direct peering to major TRON Super Representative nodes. Redundant BGP routes across two transit providers per region. Cross-region latency is sub-180ms between any two nodes.

10 Gbps Dual BGP <180ms

Monitoring

Continuous health checks every 15 seconds from three independent monitoring locations. Metrics include block height parity, mempool depth, gas price oracle accuracy, and swap throughput. Alerts fire within 30 seconds of anomaly detection.

15s Interval 3 Monitors 30s Alert

Failover

Automatic failover between primary and backup relays within each region. Detection time is 4 seconds; cutover is sub-500ms. In-flight swaps are preserved: the backup relay picks up unconfirmed transactions and resumes processing without data loss.

4s Detect <500ms Cutover Zero Loss

Security

All node-to-node communication is encrypted via mTLS with certificate pinning. Nodes authenticate to the TRON network using hardware-backed HSMs for transaction signing keys. SSH access is restricted to a bastion host with hardware MFA enforcement.

mTLS HSM Bastion + MFA

Deployment

Rolling deployments with canary testing. New versions are deployed to a single backup relay first, monitored for 6 hours, then promoted region by region. Rollback is automated if error rates breach 0.01% during the canary window.

Canary 6h Bake Auto-Rollback