Design routing and recovery around your operational requirements.
Applications that rely on real-time market data cannot afford unexpected downtime. CoinAPI provides multiple deployment options to help customers build highly available infrastructure.
Combine GeoDNS routing, regional endpoints, and customer-controlled failover to reduce dependence on a single network path.
Choose the routing, monitoring, and recovery strategy that fits your production environment.
High availability is the practice of designing systems that continue operating when part of the infrastructure becomes unavailable.
Instead of relying on a single endpoint or network path, applications use redundant connections that can continue serving requests or streaming market data if connectivity problems occur.
CoinAPI supports this approach through GeoDNS routing and regional endpoints for REST and WebSocket APIs.
Implementation differs slightly between REST and WebSocket APIs, but the overall design principles remain the same.
Request-based market data retrieval with regional endpoints and GeoDNS.
Unified real-time streaming with regional endpoints and GeoDNS.
Exchange-specific streaming with dedicated endpoint selection.
Each API has its own implementation guide with configuration examples, recommended monitoring, and failover strategies.
| API | Typical use case | Regional endpoints | GeoDNS | Failover |
|---|---|---|---|---|
| REST API | Request-based market data retrieval | Available | Available | Customer-managed |
| WebSocket V1 | Unified real-time streaming | Available | Available | Customer-managed |
| WebSocket DS | Exchange-specific streaming | Available | Exchange-specific endpoint | Customer-managed |
CoinAPI offers both GeoDNS endpoints and dedicated regional endpoints. GeoDNS automatically routes requests to an appropriate region based on network conditions and client location, making it a good default option for most applications.
For customers requiring greater control, regional endpoints let applications explicitly connect to infrastructure located in EMEA, APAC, or NCSA. This makes it possible to build deterministic failover strategies, test regional behavior, and integrate endpoint selection into existing infrastructure.
Regional endpoints are especially useful for teams that need predictable routing behavior across production, staging, and disaster recovery environments. They also help infrastructure teams validate latency, availability, and failover logic per region instead of relying only on automatic routing decisions. For most customers, GeoDNS is the recommended starting point, while regional endpoints are best suited for latency-sensitive or enterprise deployments with stricter operational requirements.
Choose GeoDNS when you need:
Choosing between GeoDNS and regional endpoints depends on how much control you need over routing and recovery.
Two deployment strategies are commonly used when designing highly available systems.
Multiple application paths remain active simultaneously, each connected to different CoinAPI regions. This approach provides the fastest recovery and the highest level of resilience but requires independent customer-side infrastructure, monitoring, and traffic management.
One endpoint serves production traffic while another remains available as a standby. If the primary path becomes unavailable, traffic is redirected to the secondary endpoint. This approach is simpler to operate and may reduce duplicated API usage, although failover can take slightly longer.
High availability depends on more than multiple endpoints. Applications also need continuous health monitoring to determine when failover should occur.
Monitoring these metrics allows customer infrastructure to detect degraded connections and automatically route traffic through an alternative endpoint.
CoinAPI provides the infrastructure needed to build resilient applications, while customers retain full control over how failover is implemented.
Because every production environment is different, CoinAPI does not enforce a specific architecture. Customers are free to design failover procedures that match their own infrastructure, recovery objectives, and operational requirements.
Follow the implementation guidance for your delivery method and build the monitoring and failover strategy that matches your environment.
Learn how to configure GeoDNS and regional REST endpoints for resilient request-based market data access.
Configure resilient real-time streaming using regional WebSocket endpoints, heartbeat monitoring, and customer-managed failover.
Build highly available exchange-specific streaming infrastructure using regional WebSocket DS endpoints.
Organizations with strict availability requirements may require dedicated infrastructure, custom deployment architectures, or enterprise-grade resilience planning.
CoinAPI Enterprise plans support dedicated environments and deployment options designed for organizations operating mission-critical financial systems.
If your infrastructure requires higher levels of availability or customized deployment strategies, our team can help design an architecture that aligns with your operational requirements.
Even well-designed high availability architectures benefit from operational visibility.
Subscribe to the CoinAPI Status Page for updates about incidents, scheduled maintenance, regional availability, and service status changes.
