Uptime history
Healthy and degraded checks across monitored features. Gaps are excluded from uptime.
49.2% uptime
1 month
1 Oct 2026 UTCGray: no recorded checksNow
Jungle Testnet
73e4385a2708e6d7048834fbc1079f2fabb17b3c125b146af438971e90716c4d
https://jungle.eosusa.io
Health, freshness, CORS, and recent check history for this endpoint.
- Producer
- ivote4eosusa
- Chain
- Jungle Testnet
- Reported chain history
- Full
- Location
- Greenville,SC,USA
Current service health
Chain API
HealthyChain API responded normally
- Checked
- Latency
- 116 ms
- Browser requests
- Allowed
- Version
- Spring v1.2.3-alpha1
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 116 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 109 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 103 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 113 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 112 ms | Allowed | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 109 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 112 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 329 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | Chain API responded normally | 112 ms | Allowed |
Account Query
Healthyaccount-query responded normally
- Checked
- Latency
- 349 ms
- Browser requests
- Allowed
- Version
- Spring v1.2.3-alpha1
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 349 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 374 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 338 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 381 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 358 ms | Allowed | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 375 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 368 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 335 ms | Allowed | |
| Healthy | Spring v1.2.3-alpha1 | account-query responded normally | 366 ms | Allowed |
History API
InvalidHTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.
- Checked
- Latency
- 332 ms
- Browser requests
- Blocked
- Version
- Spring v1.2.3-alpha1
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 332 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 343 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 102 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 343 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 339 ms | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 109 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 115 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 322 ms | Blocked | |
| Invalid | Spring v1.2.3-alpha1 | HTTP 503 on /v1/history/get_actions instead of a valid history-v1 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 345 ms | Blocked |
Hyperion API
InvalidHTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs.
- Checked
- Latency
- 110 ms
- Browser requests
- Blocked
- Version
- Unknown
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 110 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 108 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 322 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 112 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 110 ms | Blocked | |
| Down | Unknown | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 353 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 313 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 345 ms | Blocked | |
| Invalid | Unknown | HTTP 503 on /v2/health instead of a valid hyperion-v2 response. The server or its upstream node is failing. Check the node, the proxy and the server logs. | 109 ms | Blocked |