Web3 node analytics: track your 1inch RPC usage in Observability
The Observability dashboard now has a dedicated Web3 tab — see calls by method, error rate, and total requests for your 1inch RPC nodes, broken down by chain, app, response code, and protocol type.
If you use 1inch RPC nodes, you can see exactly how your traffic behaves — in near real time, filtered to the chain, app, and time range you care about — without emailing support or guessing where errors come from.
What you can do
The Web3 tab surfaces the three metrics that matter most for RPC node usage:
- Calls by method — request volume over time, per RPC method (e.g.
eth_call,eth_getLogs,eth_blockNumber). - Error rate — the share of failing calls, so a spike is obvious at a glance.
- Requests — total number of RPC requests across the selected range.
Break it down the way you work
Every metric can be split across the dimensions you actually debug and report on:
- Chains — see which networks drive your RPC traffic.
- Apps — attribute usage to a specific application.
- Response codes — separate healthy
200s from500/503failures. - Protocol types — compare
HTTPvsWStraffic.
Get started
- Open Observability in the portal and switch to the Web3 tab.
- Pick a time range and filter by RPC method, protocol type, chain, app, or organisation.
- Read calls by method, error rate, and total requests — then drill into the chain, app, response-code, and protocol-type breakdowns.
Also new: average latency in Overview
Shipping alongside the Web3 tab, the Overview tab now tracks average latency over time. Latency data is available from 10 July 2026, 06:00 UTC onward and, like every other Overview metric, can be filtered by time range, product, app, and response code.
