Crypto custody sits at the intersection of financial services and distributed systems — an environment where the cost of downtime is measured not just in lost revenue but in regulatory exposure, custodial liability, and the erosion of client trust in a sector that is built on promises of security and availability. Institutional clients holding digital assets under a custody arrangement have a simple expectation: that their assets are safe, accessible on demand, and accurately reflected in their portfolio at all times.
When a crypto custody platform experiences a partial or total outage, those expectations fail simultaneously. A wallet balance API returning stale data means clients can't accurately value their holdings. A withdrawal processing failure means assets that a client is trying to transfer for settlement purposes are inaccessible. A key management service disruption means the signing infrastructure behind every transaction is unavailable — a failure that halts all operations, not just individual requests.
Custody platforms are also heavily scrutinised by regulators who expect documented evidence of operational resilience. An incident that surfaces from a client complaint rather than an internal monitoring alert is an incident that damages your regulatory standing as well as your client relationships.
This guide covers the specific uptime risks of crypto custody platforms, what to monitor across your custody infrastructure, and how to configure Vigilmon to protect the operational availability and client trust that institutional custody depends on.
Why Crypto Custody Monitoring Is in a Category of Its Own
Asset Inaccessibility Is a Custodial Failure, Not an IT Issue
In most industries, a backend API failure is an operational problem. In crypto custody, a failure that blocks client access to their assets is a custodial failure with potential legal and regulatory consequences. Clients who cannot withdraw or transfer their assets on schedule may face settlement failures in their own downstream operations — with financial and reputational consequences that extend well beyond your platform.
Sub-two-minute detection of custody API failures is the minimum standard for institutional operations. The faster you detect and begin remediation, the more options you have before a client is materially affected.
Key Management Infrastructure Has Zero Tolerance for Degradation
Hardware Security Modules (HSMs), multi-party computation (MPC) key management services, and signing infrastructure are the heart of every crypto custody operation. Degradation in key management doesn't just slow things down — it stops them entirely. A custody platform without functioning signing infrastructure cannot process any transaction, regardless of how healthy the rest of the stack appears.
Key management services must be monitored independently of application-layer APIs, with the shortest possible check intervals and the most direct escalation paths.
Regulatory Reporting Depends on Real-Time Data Accuracy
Institutional custody clients rely on your platform's portfolio data for their own regulatory reporting, accounting, and risk management. A balance reporting API that serves stale or inaccurate data creates compliance problems downstream for clients who use it for mark-to-market valuations, regulatory filings, or fund NAV calculations. Data accuracy failures are often discovered hours or days after the fact — by which point client and regulatory consequences have already accumulated.
What to Monitor in a Crypto Custody Platform
1. Key Management and Signing Infrastructure
The signing layer is the most critical component in the custody stack. Monitor:
- HSM health and availability endpoints
- MPC key generation and signing service APIs
- Signing coordinator health (quorum management services)
- Key material backup and recovery service health
- HSM cluster status and replication endpoints
Any degradation in key management must trigger an immediate P0 alert with escalation to the head of technology and the chief risk officer. There is no graceful degradation path for signing infrastructure.
2. Wallet Balance and Portfolio Reporting APIs
Clients depend on balance accuracy for valuation, reporting, and transaction planning. Monitor:
- Real-time wallet balance query endpoints (per asset, per sub-account)
- Portfolio aggregation and reporting APIs
- Historical transaction and statement retrieval endpoints
- Multi-asset valuation and mark-to-market endpoints
- Sub-custodian position reconciliation APIs
Heartbeat monitoring on your balance reconciliation jobs catches the case where on-chain data stops updating before clients notice discrepancies — or before your compliance team notices them in the reconciliation report.
3. Transaction Submission and Processing APIs
Client withdrawal and transfer requests flow through transaction processing APIs that must remain available during settlement windows. Monitor:
- Transaction initiation and request submission endpoints
- Multi-sig approval and co-signer coordination APIs
- Transaction broadcast endpoints (per blockchain network)
- Transaction status and confirmation tracking APIs
- Fee estimation and network selection endpoints
A transaction processing failure during a client's settlement window — when they need to deliver assets to a counterparty — is a contractual failure with financial consequences for the client and reputational consequences for you.
4. Blockchain Node Connectivity
Custody platforms depend on reliable connections to blockchain nodes for transaction submission and on-chain state validation. Monitor:
- Primary and backup RPC node health endpoints
- On-chain transaction confirmation polling latency
- Block synchronisation status across monitored networks
- Smart contract interaction endpoints (for DeFi custody)
- Cross-chain bridge integration health (for multi-chain custody)
Node connectivity failures that persist silently cause your platform to serve stale blockchain state — balances that haven't updated, confirmations that haven't been received, and deposits that haven't been credited.
5. Client Portal and Authentication Services
Institutional clients access portfolio data and initiate transactions through authenticated portals. Monitor:
- Client authentication and session management endpoints
- Multi-factor authentication service health
- API key management and credential rotation endpoints
- SSO integration health (for enterprise clients)
- IP allowlisting and access control enforcement endpoints
A portal authentication failure locks all clients out simultaneously — the most visible possible incident in a custody relationship.
6. Compliance and Regulatory Reporting Infrastructure
Custody platforms maintain transaction monitoring, sanctions screening, and regulatory reporting systems. Monitor:
- Transaction screening API health (Chainalysis, Elliptic integrations)
- AML monitoring service endpoints
- Regulatory report generation APIs
- Audit trail write endpoints (every transaction must be logged)
- VASP registry and counterparty verification APIs
Compliance infrastructure failures must trigger immediate alerts to the compliance team in addition to engineering — regulatory breach risk does not wait for the IT incident queue.
7. Client Notification and Communication Services
Custody clients expect immediate confirmation of transaction execution, deposits, and withdrawals. Monitor:
- Transaction confirmation notification endpoints (email, webhook, API push)
- Deposit detection and alert service health
- Client webhook delivery service reliability
- Statement generation and scheduled report delivery endpoints
- Incident communication service health
Delayed transaction notifications create client uncertainty about asset state — particularly damaging in volatile market conditions where confirmations have time value.
The Operational and Regulatory Mathematics of Custody Monitoring
| Failure type | Undetected for 30 minutes | Detected in 2 minutes | |---|---|---| | Key management degradation | All transactions halted; client withdrawals blocked | P0 declared; CTO and CRO alerted; continuity procedure activated | | Balance API serving stale data | Clients making decisions on incorrect valuations | Data team notified; clients informed of data lag; sources reviewed | | Transaction processing down | Settlement failures; counterparty defaults; client financial loss | P1 declared; manual processing activated; clients notified | | Node connectivity lost | On-chain state stale; deposits unconfirmed; balances diverging | Infrastructure team alerted; failover node activated | | Compliance screening failing | Unscreened transactions proceeding; regulatory exposure | Compliance officer notified; transaction processing paused |
In custody operations, the cost of a 30-minute undetected failure is not just the service disruption — it is the regulatory and client relationship consequence that follows the incident disclosure.
Vigilmon Setup for Crypto Custody Teams
Step 1: Map the Custody Critical Path
The custody critical path runs from client request to confirmed on-chain execution. Map each component:
- Client authentication and portal access
- Balance query and portfolio data retrieval
- Transaction initiation and co-signer approval
- Key management and signing
- Transaction broadcast to blockchain network
- On-chain confirmation and status update
- Client notification and audit trail logging
Add a Vigilmon monitor for each stage. Key management monitors use 30-second check intervals. Client authentication and transaction processing use 60-second checks. All use immediate escalation to engineering on-call.
Step 2: Add Heartbeat Monitors for Custody Batch Processes
Custody platforms run critical batch processes for reconciliation, reporting, and compliance. Add heartbeat monitors for:
- Daily balance reconciliation jobs
- On-chain transaction confirmation sweep jobs
- Regulatory report generation jobs
- Audit log archival jobs
- Sub-custodian position reconciliation jobs
If a reconciliation job fails to call Vigilmon within its expected window, alert the compliance and operations teams immediately — reconciliation failures compound with each missed run.
Step 3: Monitor Each Blockchain Network Independently
Multi-chain custody platforms need per-network monitoring:
- Bitcoin node health and mempool connectivity
- Ethereum node health and smart contract call latency
- Each additional chain monitored independently
Cross-chain custody dependencies mean a failure on one network can affect clients with multi-chain portfolios even if the primary node is healthy.
Step 4: Configure a Client-Facing Status Page
Institutional clients expect transparency during incidents. Configure a Vigilmon status page with groups for:
- Platform access and authentication
- Transaction processing
- Balance and portfolio data
- Blockchain network connectivity
Proactive status communication during incidents is a regulatory expectation as well as a client service standard. Publish the status page URL in your client onboarding documentation and SLA agreements.
Step 5: Set Alert Escalation by Custody Risk Level
- Key management or signing infrastructure degraded: Immediate P0 alert to engineering on-call, CTO, CRO — all channels
- Transaction processing down: Immediate P1 alert to engineering on-call + operations lead
- Balance API stale more than 5 minutes: Alert to data engineering + compliance
- Compliance screening failing: Immediate alert to compliance officer + engineering
- Node connectivity lost: Alert to infrastructure team within 2 minutes
- SSL certificate expiry under 30 days: Weekly digest to security team
Getting Started
Crypto custody platforms operate with a standard that most software companies never encounter: the expectation that client assets are continuously accessible, accurately reported, and securely managed — with zero tolerance for the silent failures that most application monitoring systems miss. The monitoring discipline appropriate for consumer software is not adequate for infrastructure that holds institutional capital under custodial arrangements.
Vigilmon gives your custody engineering and operations teams the visibility to detect key management degradation, transaction processing failures, balance data staleness, and compliance infrastructure dropouts before they become client incidents, regulatory events, or SLA breaches.
Start monitoring your crypto custody platform at vigilmon.online — free for up to five monitors, one-minute check intervals, Slack alerts, and a status page included. No credit card required.
Tags: #cryptocustody #digitalassets #blockchain #HSM #MPC #uptime #monitoring #fintech #institutional