solanaRpcLatencyWatcher

The solanaRpcLatencyWatcher function monitors the latency between Portal and external RPC providers, helping you track indexing performance.

Import

import { solanaRpcLatencyWatcher } from '@subsquid/pipes/solana'

Signature

function solanaRpcLatencyWatcher(options: {
  rpcUrl: string[]
}): Transformer

Parameters

Parameter	Type	Description
`rpcUrl`	`string[]`	Array of RPC endpoint URLs to monitor

Return Value

Returns a query-transformer combo that already includes the block query it needs. Pass it directly as the source’s outputs. You can chain .pipe() transforms to it.

Output Data Structure

Each output contains:

{
  number: number,           // Slot number
  timestamp: Date,          // Block timestamp
  portal: {
    receivedAt: Date,       // When the block arrived from the Portal
  },
  rpc: Array<{
    url: string,            // RPC endpoint URL
    hash?: string,          // Not set on Solana: slot update notifications carry no hash
    receivedAt?: Date,      // When the block was received from this RPC
    portalDelayMs: number,  // Delay between RPC arrival and Portal availability (ms)
  }>
}

Basic Usage

import { solanaPortalStream, solanaRpcLatencyWatcher } from '@subsquid/pipes/solana'

const stream = solanaPortalStream({
  id: 'solana-latency',
  portal: 'https://portal.sqd.dev/datasets/solana-mainnet',
  outputs: solanaRpcLatencyWatcher({
    rpcUrl: ['https://api.mainnet-beta.solana.com'],
  }),
})

for await (const { data } of stream) {
  if (!data) continue

  console.log(`Slot: ${data.number}`)
  console.table(data.rpc)
}

Example Output

-------------------------------------
BLOCK DATA: 369,377,455 / Fri Sep 26 2025 15:31:36 GMT+0400
┌───┬─────────────────────────────────────┬──────────────────────────┬───────────────┐
│   │ url                                 │ receivedAt               │ portalDelayMs │
├───┼─────────────────────────────────────┼──────────────────────────┼───────────────┤
│ 0 │ https://api.mainnet-beta.solana.com │ 2025-09-26T11:31:37.075Z │ 358           │
└───┴─────────────────────────────────────┴──────────────────────────┴───────────────┘

Multiple RPC Endpoints

Monitor multiple RPC providers simultaneously:

const stream = solanaPortalStream({
  id: 'solana-latency',
  portal: 'https://portal.sqd.dev/datasets/solana-mainnet',
  outputs: solanaRpcLatencyWatcher({
    rpcUrl: [
      'https://api.mainnet-beta.solana.com',
      'https://solana-mainnet.rpc.extrnode.com',
    ],
  }),
})

Metrics Integration

Export latency data to Prometheus via the built-in metrics registry. See the Data freshness monitoring guide for the full example:

import { solanaPortalStream, solanaRpcLatencyWatcher } from '@subsquid/pipes/solana'
import { metricsServer } from '@subsquid/pipes/metrics/node'

const stream = solanaPortalStream({
  id: 'solana-latency',
  portal: 'https://portal.sqd.dev/datasets/solana-mainnet',
  outputs: solanaRpcLatencyWatcher({
    rpcUrl: ['https://api.mainnet-beta.solana.com'],
  }).pipe({
    profiler: { name: 'expose metrics' },
    transform: (data, { metrics }) => {
      if (!data) return

      for (const rpc of data.rpc) {
        metrics
          .gauge({
            name: 'rpc_latency_ms',
            help: 'RPC Latency in ms',
            labelNames: ['url'],
          })
          .set({ url: rpc.url }, rpc.portalDelayMs)
      }

      return data
    },
  }),
  metrics: metricsServer({ port: 9090 }),
})

How It Works

The RPC latency watcher:

Subscribes to slot updates via WebSocket (slotsUpdatesSubscribe)
Listens for optimisticConfirmation events from each RPC
Compares the arrival time of blocks between RPC and Portal
Reports the delay as portalDelayMs

The measured values include client-side network latency. For RPC, only the arrival time of the block is measured. This does not capture the node’s internal processing latency.

Use Cases

Performance monitoring - Track indexing latency in production
RPC comparison - Compare performance across different RPC providers
Alerting - Trigger alerts when latency exceeds thresholds
Optimization - Identify bottlenecks in your indexing pipeline

Pipes SDK

Squid SDK

Import

Signature

Parameters

Return Value

Output Data Structure

Basic Usage

Example Output

Multiple RPC Endpoints

Metrics Integration

How It Works

Use Cases

​Import

​Signature

​Parameters

​Return Value

​Output Data Structure

​Basic Usage

​Example Output

​Multiple RPC Endpoints

​Metrics Integration

​How It Works

​Use Cases

Import

Signature

Parameters

Return Value

Output Data Structure

Basic Usage

Example Output

Multiple RPC Endpoints

Metrics Integration

How It Works

Use Cases