Uptime history
Healthy and degraded checks across monitored features. Gaps are excluded from uptime.
78.9% uptime
14 days
16 Oct 2026, 08 UTCGray: no recorded checksNow
Antelope node health, status, and history for operators and developers.
f16b1833c747c43682f4386fca9cbb327929334a762755ebec17f6f23c9b8a12
Health, freshness, CORS, and recent check history for this endpoint.
Healthy and degraded checks across monitored features. Gaps are excluded from uptime.
78.9% uptime
14 days
Chain API responded normally
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 357 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 323 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 321 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 322 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 342 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 366 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 351 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | Chain API responded normally | 329 ms | Allowed |
account-query responded normally
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 345 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 378 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 355 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 382 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 344 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 430 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 368 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | account-query responded normally | 352 ms | Allowed |
history-v1 responded normally
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 124 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 347 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 126 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 125 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 130 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 373 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 126 ms | Allowed | |
| Healthy | Spring v1.3.1wax02 | history-v1 responded normally | 128 ms | Allowed |
hyperion-v2 responded normally
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 155 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 150 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 151 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 158 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 151 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 153 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 161 ms | Allowed | |
| Healthy | 3.5.0-3-dirty | hyperion-v2 responded normally | 388 ms | Allowed |
HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 111 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 113 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 113 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 102 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 104 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 153 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 113 ms | Allowed | |
| Invalid | Unknown | HTTP 404 on /atomicassets/v1/config. The server has no route for this atomic-assets-api check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 105 ms | Allowed |