When infrastructure breaks, you need answers you can stand behind.
An RPC incident can be over before your team understands its impact. Magma brings provider health, routing decisions and connectivity records together across Magma-managed RPC access, your existing providers and private nodes, or a hybrid configuration. Available evidence and operational responsibilities follow your deployment and commercial scope.
Know what happened. Understand what reached your customers. Be better prepared to explain it.
- Multi-provider visibility
- Enterprise incident response
- SOC 2 Type II and ISO/IEC 27001
Step 1 of 4: RPC infrastructure operational
Blockchain RPC Infrastructure
Ethereum
- Provider AHealthy
- Provider BHealthy
- Private NodeHealthy
Magma Smart Router
- Provider health
- Routing decisions
- Recovery signals
- Operational metrics
Routing to Provider A
Customer Operations
- Investigation
- Customer impact assessment
- Internal incident review
Fixing the outage is only half the job.
When a blockchain infrastructure incident occurs, restoring service is the immediate priority.
But once traffic is moving again, another set of questions begins.
Customers want to know whether they were affected.
Engineering leaders want to know what failed and why.
Security and risk teams need evidence of the controls that were in place.
Vendor managers want to understand whether an RPC provider met its commitments.
And when regulators or auditors become involved, assumptions and screenshots are rarely a satisfying substitute for a documented investigation.
The problem gets harder when blockchain infrastructure spans multiple vendors, networks, and internal systems.
The investigation takes too long
Logs, metrics, provider dashboards, and application errors are scattered across different systems.
Your engineers spend valuable time reconstructing the incident instead of improving the infrastructure.
Customer impact is unclear
An upstream provider may fail while the application continues operating through another one.
Without the right measurements, teams can struggle to distinguish an upstream failure from a customer-facing interruption.
Evidence is incomplete
After the incident, teams may need to reconstruct the timeline, explain routing decisions, and document which systems were affected.
If useful evidence was never collected, it can be difficult or impossible to recover later.
An incident you can't explain is an incident you haven't fully understood.
One infrastructure layer. A clearer picture of what happened.
Smart Router operates between your systems and your configured RPC providers.
That position gives it visibility into the infrastructure behavior surrounding the requests it serves, including provider selection, failures, retries, health conditions, and applicable validation signals.
- 01Observe
See provider health across your infrastructure
Monitor availability, latency, upstream errors, and relevant health signals for configured providers.
Understand when a provider becomes slow, unavailable, rate-limited, or falls behind the blockchain.
- 02Investigate
Understand routing and recovery
Review metrics showing when requests required additional attempts and whether retry or failover recovered them.
Separate underlying provider problems from the requests that ultimately failed at the customer-facing layer, where supported by the available measurements.
- 03Understand Impact
Investigate inconsistent blockchain data
Use freshness and configured cross-validation signals to identify relevant disagreements or problems with RPC data quality.
Not every infrastructure incident is a hard outage. An endpoint can respond successfully while returning unreliable information.
- 04Document
Support incident review with operational evidence
Use metrics, traces, logs, and available exports as inputs to incident investigation, reliability reviews, and documentation requested by customers or internal teams.
With the appropriate Enterprise service, Magma can also help operate the infrastructure and respond to incidents.
Better evidence starts with better visibility into the infrastructure serving your traffic.
Related: Incident Analysis · Compliance Reports · Metrics reference
A provider failed. Did your customers actually experience an outage?
An upstream failure and a customer-facing failure are not necessarily the same event.
A reliable incident review needs to distinguish what happened to the underlying provider from what happened to the requests your application depended on.
Scenario: Provider outage, customer traffic recovered
Infrastructure
- Provider AUnavailable
- Provider BHealthy
- Provider CHealthy
Routing activity: Eligible traffic moved from Provider A to Provider B
- 14:02:10Provider A begins returning upstream errors.
- 14:02:12Smart Router selects another eligible provider.
- 14:02:13Provider B serves recovered requests.
- 14:04:40Provider A returns to a healthy state.
Upstream incident detected
Eligible traffic recovered through another provider
Customer-facing impact: No failures observed in this illustrative scenario
Evidence categories
- Provider error signal
- Router retry/failover activity
- Recovered request measurements
- Provider health timeline
What an investigation needs to establish
Illustrative investigation summary- Affected blockchain
- Ethereum (example)
- Incident time window
- 14:02:10 to 14:04:40
- Involved RPC providers
- Provider A (failed), Provider B (served)
- Observed failure mode
- Upstream errors from Provider A
- Routing response
- Retry and failover to another eligible provider
- Customer-facing impact
- No failures observed in this example
- Data consistency signals
- Not applicable
- Recovery observations
- Provider A healthy again at 14:04:40
- Items requiring further investigation
- Cause of Provider A errors, with the vendor
Example data shown for illustration. This is a demonstration of incident evidence categories, not a live dashboard or automated report-generation product.
The questions your incident review needs to answer.
Different teams need different answers after a blockchain infrastructure problem.
The infrastructure team wants to understand the failure.
The business wants to understand the impact.
Customers want to understand the disruption.
Auditors and risk teams may need evidence that monitoring, resilience, and response controls were operating.
Magma provides operational signals that can support these investigations.
- 01What failed?
- Use available provider error, latency, freshness, and health measurements to investigate the affected upstreams and blockchain interfaces.
- 02What did the infrastructure do?
- Examine routing and retry signals to understand whether requests were recovered through another provider or remained unsuccessful.
- 03What reached the customer?
- Use client-facing request metrics and relevant application telemetry to assess which failures or delays may have affected your services.
- 04What supports the conclusion?
- Bring together the relevant metrics, traces, logs, and investigation findings into a documented incident review.
01
Provider Signal
Errors, latency, availability, chain freshness
02
Routing Response
Provider selection, retries, failover
03
Customer Outcome
Recovered traffic, failed requests, latency impact
04
Incident Review
Timeline, findings, supporting evidence, follow-up actions
Evidence doesn't replace investigation. It gives your investigation a stronger foundation.
Further reading: Monitoring RPC health
Your RPC providers see their infrastructure. You need to understand yours.
When your applications depend on multiple RPC providers, each vendor may give you a different view of the same incident.
One provider reports a service disruption.
Another reports healthy endpoints.
Your application logs show timeouts.
And your operations team needs to determine whether the problem was isolated, widespread, or successfully handled by failover.
Magma operates above the providers your applications use.
That shared routing layer helps teams evaluate the behavior of configured upstream sources in the context of the traffic actually passing through Smart Router.
Fragmented visibility
- Separate views
- Manual correlation
- Incomplete customer-impact context
Magma operational layer
- Shared RPC telemetry
- Routing and recovery visibility
- Better incident context
Provider dashboards remain useful. The shared layer adds context across them.
Independent operational perspective
Understand provider behavior without relying exclusively on each vendor's own status and performance dashboards.
Multi-chain context
Examine routing and health signals across supported blockchain networks and interfaces.
Better provider conversations
Use the available measurements to discuss recurring issues, service quality, and operational follow-up with your RPC vendors.
A provider status page describes the provider's service. Your incident review needs to describe what happened to your systems.

Provider disruption requires routing evidence, not assumptions.
On December 3, 2025, Ethereum's Fusaka upgrade disrupted RPC infrastructure.
According to Magma's published Fireblocks case study, its Ethereum RPC provider pool experienced disruption, while other endpoints fell behind the chain.
Smart Router automatically directed eligible traffic away from unavailable or stale providers and toward healthier alternatives.
No verified customer uptime result is presented.
The case demonstrates why cross-provider visibility and automated routing matter during a major infrastructure disruption.
Understanding which providers became unavailable, which alternatives remained healthy, and how traffic was handled is also central to a meaningful incident review.
- Provider measurements require verification
- Provider disruption
- No verified customer uptime result
- Result withheld
Provider measurements require verification
No verified customer uptime result
The operational result matters first. The ability to explain the infrastructure response matters afterward.
Read the Fireblocks case studyEthereum Fusaka upgrade
December 3, 2025- Illustrative stateUnavailable
- Illustrative stateStale
- Illustrative stateHealthy
healthy sources only
- 1.Provider disruption
- 2.Automatic routing response
- 3.Outcome verification pending
Trusted in production by












When your customers and risk teams ask for evidence, infrastructure visibility matters.
For financial platforms, incident management does not end when an alert closes.
Internal security reviews, customer assurance processes, vendor oversight, and regulatory examinations can all require a clear explanation of how critical infrastructure behaved.
Blockchain connectivity is part of that operating environment.
The relevant questions often concern third-party dependencies, availability, data integrity, incident response, and the controls around critical systems.
Magma's RPC telemetry and operational processes can help teams prepare the infrastructure-related evidence used in those reviews.
Operational resilience reviews
Understand provider failures, routing behavior, recovery mechanisms, and observed customer-facing impact.
Third-party provider oversight
Use available measurements to review the reliability and behavior of the RPC vendors your infrastructure depends on.
Data integrity controls
Use configured validation and provider-disagreement signals as supporting evidence for controls around sensitive blockchain reads.
Relevant to regulated digital asset infrastructure
Frameworks such as DORA, MiCA, and internal financial control requirements can increase the importance of operational resilience, incident documentation, third-party oversight, and reliable records.
Magma provides infrastructure telemetry that can support related control and review processes.
Your compliance and legal teams remain responsible for determining the evidence required by the rules that apply to your organization.
Your infrastructure partner should be ready for your security review, too.
When you depend on a third party to help operate critical blockchain infrastructure, its own security practices matter.
Magma Devs has completed a SOC 2 Type II examination and holds ISO/IEC 27001 certification.
Our security program covers areas including access management, operational monitoring, infrastructure controls, development practices, incident response, and vendor oversight.
Relevant security documentation is available through our Trust Center and request process.

SOC 2 Type II
Independent examination of Magma's applicable security controls over an audit period.

ISO/IEC 27001
Certification of Magma's information security management system within its defined scope.
Our certifications describe Magma's security program. They do not certify that every customer deployment or use case is compliant with every regulation.
An incident needs more than telemetry. It needs someone responsible for responding.
Smart Router provides the technical signals that help teams understand their blockchain connectivity.
But incident response also requires ownership.
Someone must investigate the problem, evaluate the impact, coordinate recovery, and communicate findings.
Magma offers Enterprise deployments with managed infrastructure, continuous monitoring, and 24/7 incident response under the applicable service agreement.
For teams that do not want to own another critical infrastructure system internally, this brings operational responsibility together with the technology serving their RPC traffic.
- Infrastructure monitoring
- Monitoring of the managed routing environment and relevant infrastructure health signals.
- Incident response
- Operational response to incidents affecting managed services, according to the agreed support and escalation arrangements.
- Engineering support
- Technical assistance for routing configurations, providers, integrations, and incident investigation.
- Ongoing operations
- Management of applicable infrastructure updates and operational maintenance under the selected service.
Your team remains responsible for its application and business processes. Magma can take responsibility for the managed infrastructure layer and the agreed operational support around it.
Discuss managed infrastructureYour team
Customer Systems
- Business workflows
- Customer-facing operations
- Financial decisions
Magma
Magma Managed RPC Infrastructure
- Provider orchestration
- Monitoring
- Failover
- Operational response
From operational telemetry to audit-ready evidence workflows.
We're extending Magma's operational capabilities to make incident reviews, provider accountability, and audit preparation more straightforward.
The direction is a connected evidence experience built on the routing and monitoring infrastructure already in production.
Structured incident reports
On the RoadmapMake it easier to turn incident metrics and investigation findings into clear summaries explaining the affected infrastructure, timeline, recovery actions, and observed impact.
Regulatory evidence packages
On the RoadmapDevelop structured evidence exports aligned with relevant operational resilience and record-keeping review needs, including DORA, MiCA, and ICFR-related control processes.
Access and configuration audit logs
On the RoadmapProvide stronger visibility into relevant platform access and configuration changes, including historical records and API-based access to audit information.
Provider SLA scorecards
On the RoadmapMeasure applicable provider performance against defined service commitments and help customers evaluate upstream reliability over time.
Customer notifications and advanced incident analysis
On the RoadmapExpand customer-facing incident notification options and provide additional tools for correlating operational signals and investigating incidents.
Planned capabilities. Scope, delivery, and availability may change.
Frequently asked questions
Related: High Availability · Deposit Detection & Crediting · Withdrawals & Transaction Broadcasting · New Chain Listings · Data Integrity & Reconciliation · Custody Platforms · Exchanges · Data Integrity platform · Pricing · Smart Router on GitHub
If your most critical RPC provider fails tomorrow, can you prove what happened?
Tell us which blockchains, providers, and critical workflows your infrastructure depends on.
We'll help you evaluate the visibility, resilience, and evidence available across your current RPC environment, and where Magma could strengthen it.
Understand your infrastructure. Respond with confidence. Build trust through evidence.