Skip to content
Magma Devs
Solutions / High Availability

A provider outage shouldn't become your outage.

Your deposits, balance checks and withdrawals depend on reliable blockchain access. Magma combines its managed RPC provider fleet with the option to bring your existing providers and private nodes, or use a hybrid of both. Health-aware routing can recover eligible requests through suitable alternatives under configured policies, not a universal availability guarantee.

One connection. Multiple independent providers. A team that can run the infrastructure for you.

  • 284 Supported Blockchain Networks
  • Use your existing providers
  • Managed or self-hosted
Your application
Customer Application
  • Deposits
  • Balances
  • Withdrawals
Connected to one endpoint
Magma Smart Router
Routing to Provider A
Provider A
Primary
Serving
Provider B
Backup
Healthy
Private Node
Private
Healthy
Request served by Provider A

Illustrative routing flow. Not live traffic.

Proven in production

Trusted where blockchain connectivity is business-critical.

  • Kraken
  • Fireblocks
  • Galaxy
  • Hypernative
The challenge

Having backup providers isn't the same as having reliable infrastructure.

An RPC provider can go offline without warning. Another can stay online but fall behind the chain. A third can start timing out just as market activity surges.

If your engineers still need to investigate the failure, compare providers, and manually redirect traffic, your backup infrastructure is only half the solution.

For exchanges, custodians, and wallet platforms, these incidents quickly become customer-facing problems.

Offline

Provider downtime

A critical endpoint stops responding. Deposit scans, balance requests, and withdrawal workflows can be interrupted while your team investigates.

Slow

Slow or overloaded providers

Requests take too long or hit rate limits during busy periods. Users experience delays even though the blockchain itself is running.

Stale

Out-of-sync nodes

A provider responds successfully but serves outdated chain data. Your systems may act on information that is no longer current.

The real challenge isn't finding another RPC endpoint. It's making the right routing decision automatically, across every chain and provider you depend on.

How Magma works

One connection. Every available path to the blockchain.

Smart Router sits between your application and your RPC infrastructure. It continuously evaluates which providers can serve each request, then routes traffic without requiring your team to manually intervene every time an endpoint degrades.

  1. 01

    Keep the providers you already use

    Connect your existing RPC providers and private nodes to one routing layer. Magma works across multiple independent vendors and blockchain networks.

    Provider AProvider BPrivate Node
  2. 02

    Detect degraded infrastructure

    Smart Router evaluates availability, response times, chain freshness, and rate limits. A provider that is online but behind the chain does not have to remain eligible for new requests.

    AvailabilityResponse timesChain freshnessRate limits
  3. 03

    Route around the problem

    When an eligible provider fails, the router can retry through another one. For supported slow requests, it can race providers in parallel. Backup providers remain available when primary endpoints degrade.

    RetryRace in parallelBackup
  4. 04

    Keep operations under control

    Monitor provider health and routing behavior in one place. With a managed Enterprise deployment, Magma also operates the infrastructure, handles upgrades, and provides 24/7 monitoring and incident response.

    Provider healthRouting behavior
What stays connected

Reliability for the operations your customers depend on.

Deposit monitoring

Keep blockchain scanning requests moving through healthy RPC endpoints, even when an individual provider fails. Reduce the risk of interruptions in the infrastructure that monitors incoming deposits.

Balance and account visibility

Route reads away from unavailable or out-of-sync providers to help your systems retrieve timely blockchain information.

Withdrawal infrastructure

Maintain resilient access to the RPC infrastructure used for broadcasting signed transactions. Where supported, Smart Router can send transactions through multiple eligible providers.

The result is less manual provider switching, fewer infrastructure-related interruptions, and more time for your engineering team to focus on your product.

Related: Exchanges · Custody Platforms · Supported chains

FireblocksMagma-reported event account

Magma's account of routing during the Fusaka upgrade.

During Ethereum's Fusaka upgrade on December 3, 2025, Magma's account describes disruption in its Ethereum RPC provider pool. Other nodes fell behind the chain.

Smart Router automatically routed traffic to healthy providers and screened out lagging endpoints.

Numerical customer results are withheld pending measurement verification and customer approval.

Event measurements withheld pending evidence and customer approval
Provider disruption
Event measurements withheld pending evidence and customer approval
Not a verified uptime result or general SLA
Routing account
Not a verified uptime result or general SLA

Resilience isn't only about having backup providers. It's about knowing which providers are still healthy and moving traffic before an infrastructure issue reaches your customers.

Read the Fireblocks case study
Illustrative provider statesMagma-reported Ethereum Fusaka event - December 3, 2025; not an independent audit
Offline
Lagging
Healthy
Eligible routing Requires healthy alternatives

Conceptual state categories, not provider counts or failure proportions from Fusaka. No measured customer availability result is shown.

Measurement scope

Review recovery outcomes, not assumed uninterrupted service.

Retries and failovers are engineering events. What matters to your business is whether your applications continued receiving responses when an upstream provider failed.

Eligible failover

Requires a suitable healthy alternative

Recovery visibility

Review outcomes within configured request policies

Numerical recovery and downtime results are withheld pending publicly reviewable measurement evidence and release approval.

Recovery depends on compatible healthy upstreams, supported methods and configured policies. It is not an uptime guarantee.

Managed blockchain connectivity

You don't need another provider to manage. You need the entire path to work.

Adding more providers can improve redundancy. But it also creates another layer of routing policies, monitoring, retries, integrations, and incident response that somebody has to own.

Magma brings these pieces together in one infrastructure layer, built for teams that operate across multiple blockchain networks.

Use your existing providers and private nodes. Keep control of your infrastructure decisions. Let Magma handle the routing layer and, when you choose a managed deployment, the operational work behind it.

Explore deployment options
Separate connections
Provider AOwn policies, retries, monitoring
Provider BOwn policies, retries, monitoring
Private NodeOwn policies, retries, monitoring
One Magma routing layer
Smart Router
Provider A
Provider B
Private Node

Independent provider choice

Use multiple RPC vendors and your own nodes without tying your application to a single provider's infrastructure.

Built for multi-chain operations

Manage connectivity across 284 blockchain networks, including EVM and non-EVM ecosystems.

Operational ownership

Choose managed infrastructure and Enterprise incident response, or deploy the source-available router in your own environment under the applicable license.

On the Roadmap

Building the next level of operational resilience.

Multi-region managed deployments

More deployment options for customers that need geographic infrastructure redundancy.

Provider SLA visibility

Measure provider performance against contractual expectations and connect it to the availability you deliver to your own customers.

Planned capabilities. Availability and scope are subject to change.

Frequently asked questions

No. Smart Router operates above the providers and private nodes you already use. You can connect multiple vendors and maintain control over your provider relationships.

Smart Router detects failing or degraded endpoints and can route eligible requests through another healthy provider. Recovery depends on having a suitable alternative endpoint available for the requested chain and method.

Smart Router tracks provider freshness and can exclude nodes that fall behind the acceptable chain height. An endpoint returning HTTP 200 is not automatically treated as a healthy source of blockchain data.

Yes. Magma offers managed deployments, including private Enterprise hosting, infrastructure monitoring, upgrades, and incident response. Self-hosted deployment is also available under the applicable license.

No. Smart Router protects against provider and node failures. If an entire blockchain network stops operating, no RPC routing layer can restore it. Magma helps maintain access when suitable healthy providers remain available.

Customer evidence

Automatic failover, proven in published customer deployments.

How exchanges, custodians and security platforms keep blockchain connectivity reliable across multiple RPC providers without adding operational work for their engineers.

Fireblocks · Custody infrastructure

Fireblocks publicly documents its use of Smart Router.

The Fireblocks-hosted Magma guest contribution describes Smart Router beneath its applications. This documents the relationship, not a verified event performance outcome.

“Magma Devs' Smart Router has been impactful in our ability to improve node reliability and performance, allowing our team to focus fully on core innovation.”

Pavel Berengoltz, CTO & Co-Founder, Fireblocks

Read the Fireblocks Fusaka case study

Kraken · Exchange infrastructure

Runs Smart Router in production across its product suite.

Kraken added Smart Router on top of its existing systems to monitor, rank and route requests across multiple RPC providers with automatic failover.

“Integrating Magma Devs' Smart Router strengthens the resilience and reliability of our platform at global scale.”

Brett McLain, VP & Head of Payments & Blockchain, Kraken

Read the Kraken case study

Hypernative · Security monitoring

Treats on-chain data access as a reliable system component across 70+ blockchains.

Hypernative uses Smart Router for fault tolerance and deterministic failover, removing RPC behaviour as a variable in real-time threat detection.

“Smart Router allows us to treat onchain data access as a reliable system component rather than an external dependency, which is critical for real time threat detection.”

Lior Betzalel, VP R&D, Hypernative

Read the Hypernative case study

All references come from published case studies. See all case studies or read the product documentation.

Let's make your infrastructure more resilient

How many provider failures can your platform absorb without waking an engineer?

Tell us which chains, providers, and critical workflows you depend on. We'll help you evaluate where your RPC infrastructure is exposed and how Magma can strengthen it.

Discuss your RPC setup

Keep your providers. Strengthen your reliability. Focus your engineers on building your product.