Verfügbarkeitsverlauf
Gesunde und beeinträchtigte Prüfungen aller überwachten Funktionen. Lücken werden ausgeschlossen.
49.2 % Verfügbarkeit
1 Monat
1. Okt. 2026 UTCGrau: keine aufgezeichneten PrüfungenJetzt
Jungle Testnet
73e4385a2708e6d7048834fbc1079f2fabb17b3c125b146af438971e90716c4d
https://jungle.eosusa.io
Gesundheit, Aktualität, CORS und aktueller Prüfungsverlauf für diesen Endpoint.
- Produzent
- ivote4eosusa
- Kette
- Jungle Testnet
- Gemeldeter Chain-Verlauf
- Vollständig
- Standort
- Greenville,SC,USA
Aktueller Dienstzustand
Chain API
GesundChain API responded normally
- Geprüft
- Latenz
- 109 ms
- Browser-Anfragen
- Erlaubt
- Version
- Spring v1.2.3-alpha1
Letzte Prüfungen
| Status | Version | Zusammenfassung | Latenz | CORS | Geprüft |
|---|---|---|---|---|---|
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 109 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 105 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 110 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 110 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 116 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 109 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 103 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 113 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 112 ms | Erlaubt | |
| Ausgefallen | Unbekannt | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blockiert |
Account Query
Gesundaccount-query responded normally
- Geprüft
- Latenz
- 357 ms
- Browser-Anfragen
- Erlaubt
- Version
- Spring v1.2.3-alpha1
Letzte Prüfungen
| Status | Version | Zusammenfassung | Latenz | CORS | Geprüft |
|---|---|---|---|---|---|
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 357 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 362 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 370 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 349 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 349 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 374 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 338 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 381 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 358 ms | Erlaubt | |
| Ausgefallen | Unbekannt | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blockiert |
History API
UngültigHTTP 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.
- Geprüft
- Latenz
- 109 ms
- Browser-Anfragen
- Blockiert
- 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.
Letzte Prüfungen
| Status | Version | Zusammenfassung | Latenz | CORS | Geprüft |
|---|---|---|---|---|---|
| Ungültig | 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 | Blockiert | |
| Ungültig | 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. | 337 ms | Blockiert | |
| Ungültig | 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. | 342 ms | Blockiert | |
| Ungültig | 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. | 341 ms | Blockiert | |
| Ungültig | 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 | Blockiert | |
| Ungültig | 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 | Blockiert | |
| Ungültig | 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 | Blockiert | |
| Ungültig | 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 | Blockiert | |
| Ungültig | 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 | Blockiert | |
| Ausgefallen | Unbekannt | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blockiert |
Hyperion API
UngültigHTTP 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.
- Geprüft
- Latenz
- 334 ms
- Browser-Anfragen
- Blockiert
- Version
- Unbekannt
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
Letzte Prüfungen
| Status | Version | Zusammenfassung | Latenz | CORS | Geprüft |
|---|---|---|---|---|---|
| Ungültig | Unbekannt | 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. | 334 ms | Blockiert | |
| Ungültig | Unbekannt | 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. | 105 ms | Blockiert | |
| Ungültig | Unbekannt | 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. | 114 ms | Blockiert | |
| Ungültig | Unbekannt | 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. | 119 ms | Blockiert | |
| Ungültig | Unbekannt | 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 | Blockiert | |
| Ungültig | Unbekannt | 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 | Blockiert | |
| Ungültig | Unbekannt | 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 | Blockiert | |
| Ungültig | Unbekannt | 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 | Blockiert | |
| Ungültig | Unbekannt | 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 | Blockiert | |
| Ausgefallen | Unbekannt | No response within 5s. The server is down, overloaded, or a firewall is dropping connections. | — | Blockiert |