Network Availability

Overview

What it means and why it matters

Network availability describes whether a particular blockchain network can be accessed and used for an intended operation at a given time. It is not a universal yes/no property shared by all users.

How it works in practice

A gateway checks node connectivity, chain progress, transaction broadcasting, fee estimates and confirmation observation. Deposits may remain detectable while new withdrawals are unavailable, or a third-party RPC can fail while the chain itself operates normally.

Technical detail without the jargon

Measure availability separately for reads, writes, deposits and withdrawals. Compare multiple independent sources before declaring a chain outage. Fees, finality delays and congestion are degraded performance, not always complete unavailability.

A deeper point to understand

A gateway’s supported-network status should describe at least deposit observation, payment creation and withdrawals. It may be appropriate to pause one direction while preserving another. This finer-grained control helps businesses communicate accurately and avoids unnecessary disruption to merchants on healthy chains.

Common mistakes and limitations

Do not publish ‘network down’ merely because one API returned 502. Likewise, a chain that still produces blocks can be practically unusable for small-value payments if fees exceed the order value.

What to check in a real payment system

Distinguish chain-wide unavailability from your own RPC provider outage and from mere fee congestion. Test independent node views. Show whether deposits can be detected, invoices created and withdrawals processed separately for each supported network.

Related concepts

Transaction Monitoring, Blockchain Payment Monitoring, Webhook Retry.

Further reading

Google SRE Book — Monitoring Distributed Systems.