可用性历史
所有监控功能中健康和降级检查的比例。无数据时段不计入可用性。
可用性 93.4%
6个月
2026年5月1日 UTC灰色:无检查记录现在
面向运营者与开发者的 Antelope 节点健康、状态与历史监控。
aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906
此端点的健康、新鲜度、CORS 与近期检查历史。
所有监控功能中健康和降级检查的比例。无数据时段不计入可用性。
可用性 93.4%
6个月
Chain API responded normally
| 状态 | 版本 | 摘要 | 延迟 | CORS | 检查时间 |
|---|---|---|---|---|---|
| 正常 | Spring v1.2.2 | Chain API responded normally | 604 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 699 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 517 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 493 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 473 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 491 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 503 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 492 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 481 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | Chain API responded normally | 509 毫秒 | 允许 |
account-query responded normally
| 状态 | 版本 | 摘要 | 延迟 | CORS | 检查时间 |
|---|---|---|---|---|---|
| 正常 | Spring v1.2.2 | account-query responded normally | 600 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 600 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 446 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 604 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 409 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 503 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 594 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 681 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 500 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | account-query responded normally | 623 毫秒 | 允许 |
history-v1 responded normally
| 状态 | 版本 | 摘要 | 延迟 | CORS | 检查时间 |
|---|---|---|---|---|---|
| 正常 | Spring v1.2.2 | history-v1 responded normally | 584 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 714 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 518 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 489 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 499 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 511 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 579 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 501 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 509 毫秒 | 允许 | |
| 正常 | Spring v1.2.2 | history-v1 responded normally | 509 毫秒 | 允许 |
No response within 5s. The server is down, overloaded, or a firewall is dropping connections.
Request never completed
| 状态 | 版本 | 摘要 | 延迟 | CORS | 检查时间 |
|---|---|---|---|---|---|
| 宕机 | 未知 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | 阻止 | |
| 宕机 | 未知 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | 阻止 | |
| 正常 | 4.0.1 | hyperion-v2 responded normally | 590 毫秒 | 允许 | |
| 宕机 | 未知 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | 阻止 | |
| 正常 | 4.0.1 | hyperion-v2 responded normally | 595 毫秒 | 允许 | |
| 宕机 | 未知 | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | 阻止 | |
| 正常 | 4.0.1 | hyperion-v2 responded normally | 519 毫秒 | 允许 | |
| 正常 | 4.0.1 | hyperion-v2 responded normally | 503 毫秒 | 允许 | |
| 正常 | 4.0.1 | hyperion-v2 responded normally | 491 毫秒 | 允许 | |
| 正常 | 4.0.1 | hyperion-v2 responded normally | 508 毫秒 | 允许 |