Three days after launch, NodeFlare now runs 17 dedicated nodes across 5 regions.
What changed
When we launched, all requests went through Frankfurt. Fast for Europe, not ideal for the rest of the world. Today that changes.
5 regions
| Region | Chains |
|---|---|
| Frankfurt (DE) | Ethereum, Base, HyperLiquid |
| Singapore (SG) | Base, BNB, Arbitrum |
| Los Angeles (US) | Base, Avalanche |
| Falkenstein (DE) | BNB, Arbitrum, Optimism |
| London (UK) | Base, BNB, Avalanche, Arbitrum |
Your request automatically lands on the closest region. No configuration needed — it's handled at the Cloudflare edge using the datacenter's IATA code.
Avalanche C-Chain
Avalanche is now supported as the 7th chain. Fast finality, EVM-compatible, and now running across two regions (LA and London).
https://rpc.nodeflare.app/avax/v1/{YOUR_KEY}WebSocket endpoints
All chains now have dedicated WebSocket endpoints for eth_subscribe and persistent connections. Pick the region closest to your infrastructure — URLs are in each chain's docs.
Why this matters
Multi-region means lower latency for your users and automatic failover if a node goes down. We test every node every minute and track 30 days of uptime history on the status page.