Skip to main content
GET
Health Check

Overview

V2 Available: An enhanced version is available at /{network}/v2/healthcheck with metadata and API version tracking. See Health Check V2 and the V2 Migration Guide.
The Health Check endpoint allows you to verify the API status and check if a specific network is operational. This is useful for monitoring, debugging, and implementing fallback logic in your application.

Supported Networks

Response

number
HTTP status code (200 = healthy)
string
Health status message indicating the API is operational

Example Request

Example Response

Use Cases

Monitoring

Monitor API availability in your application dashboard

Fallback Logic

Implement fallback to alternative networks if one is down

Load Balancing

Route traffic based on network latency

Debugging

Verify API connectivity when troubleshooting

Implementation Example

Status Page

For real-time status updates and historical uptime data, visit our status page: https://status.fibrous.finance

Best Practices

  1. Periodic Checks
    • Check health before critical operations
    • Implement periodic health checks (every 30-60 seconds)
    • Cache health status with appropriate TTL
  2. Timeout Handling
    • Set reasonable timeout for health checks (2-5 seconds)
    • Treat timeouts as unhealthy status
    • Implement exponential backoff for retries
  3. Graceful Degradation
    • Have fallback networks configured
    • Show user-friendly messages during downtime
    • Queue operations when possible
  4. Monitoring Integration