RPCsUpdated

Songbird RPC endpoints: free public URLs by latency

HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Songbird EVM endpoint, audited every 60 seconds from 3 regions.

TL;DR. As of , Flare Foundation has the lowest median latency of the 2 free public Songbird RPC endpoints measured, 148 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/songbird-rpc. Chain ID 19. 2 public endpoints, no key: songbird-api.flare.network, rpc.au.cc. 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 →

Songbird (chain 19, SGB) is Flare Network's canary network, a production EVM-compatible chain used to test and validate Flare's FTSO oracle system before mainnet deployment. One keyless endpoint is probed continuously: the official Songbird gateway (songbird-api.flare.network/ext/C/rpc). The FTSO AU community node (songbird.rpc.ftso.au) was removed after DNS went dead.

Methodology

Songbird: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Flare Foundation leads at 148 ms; the chain-official endpoint measures 148 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against the no-key public Songbird endpoint that sustains continuous probing (2 provider: Flare Foundation official), every 60 seconds, from us-east, eu-west and Singapore. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Songbird-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: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request.
  • 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 Songbird-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to `chain="songbird"`. Provider coverage: 2 no-key public-read endpoints live today, each listed with its URL in the endpoints table on this page. FTSO AU removed after DNS went dead.

Results: 2 free public Songbird RPC endpoints ranked by p50 latency (24h, 3 regions)

Songbird RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Flare FoundationFlare Foundation official Songbird public RPC148 ms467 ms582 ms99.79% (n=4321)
2AUPublic Songbird RPC run by AU, a Flare and Songbird FTSO data provider199 ms230 ms685 ms100.00% (n=4321)

Public Songbird RPC endpoints measured

Chain ID 19, currency SGB. The 2 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.

  • Flare Foundation logoFlare Foundationhttps://songbird-api.flare.network/ext/C/rpc148 ms99.8%
  • AU logoAUhttps://rpc.au.cc/songbird199 ms100.0%

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 Songbird RPCs work without an API key?

2 endpoint sustains continuous keyless probing: Flare Foundation official (songbird-api.flare.network/ext/C/rpc). The FTSO AU community node was removed after its DNS went dead.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities