Get EL mesh aggregate health

GET /v1/eth/leak-mesh/health returns a single aggregate view of the Ethereum execution-layer leak-mesh: how many EL hosts back the mesh, how many of them are currently healthy, the combined sustained request ceiling, and the per-host RPS distribution (p50 / p95). It takes no parameters and returns one flat JSON object.

Use it as a lightweight capacity and liveness probe before fanning out traffic across the mesh. A healthy_count well below host_count, or a sharp drop in aggregate_rps_ceiling, is an early signal that the mesh is degraded and you should throttle or back off. The p50_host_rps / p95_host_rps pair lets you reason about how evenly load can be spread: a wide gap between them means a few hosts are carrying disproportionately more capacity than the median.

For the per-host breakdown behind these aggregates, see leak-mesh-hosts. To route a one-shot JSON-RPC call through a specific host, see leak-mesh-proxy (Pro+).

This endpoint takes no path, query, or body parameters.

Response fields

All error bodies use the shared envelope (error, message, request_id). See errors.md for the full envelope and handling guidance.

JavaScript (fetch)

const res = await fetch("https://api.triport.io/v1/eth/leak-mesh/health", {
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
  },
});


if (!res.ok) {
  const err = await res.json();
  throw new Error(`${res.status} ${err.error}: ${err.message}`);
}


const health = await res.json();
console.log(`${health.healthy_count}/${health.host_count} hosts healthy`);
console.log(`aggregate ceiling: ${health.aggregate_rps_ceiling} RPS`);

TypeScript SDK (@triport/sdk)

import { Triport } from "@triport/sdk";


const client = new Triport({ apiKey: process.env.TRIPORT_API_KEY! });


interface LeakMeshHealth {
  host_count: number;
  healthy_count: number;
  aggregate_rps_ceiling: number;
  p50_host_rps: number;
  p95_host_rps: number;
}


const health = await client.eth.get<LeakMeshHealth>("/v1/eth/leak-mesh/health");
console.log(`${health.healthy_count}/${health.host_count} hosts healthy`);

Python (triport-sdk)

import os
from triport import Triport


client = Triport(api_key=os.environ["TRIPORT_API_KEY"])


health = client.eth.get("/v1/eth/leak-mesh/health")
print(f"{health['healthy_count']}/{health['host_count']} hosts healthy")
print(f"aggregate ceiling: {health['aggregate_rps_ceiling']} RPS")

• The endpoint requires the basic tier or higher (eth_leak_mesh category).
• Rate limiting is RPS-per-tier with burst; there is no daily quota. A 429 rate_limited response means you should honor Retry-After and retry shortly.
• This is a read-only aggregate. For the underlying per-host list (status, sync-state, block-height) use leak-mesh-hosts; to send a JSON-RPC call through a chosen host use leak-mesh-proxy.