Verfügbarkeitsverlauf
Gesunde und beeinträchtigte Prüfungen aller überwachten Funktionen. Lücken werden ausgeschlossen.
49.8 % Verfügbarkeit
14 Tage
16. Okt. 2026, 09 Uhr 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
- 113 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 | 113 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 112 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 114 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 | 114 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 347 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 | 345 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 107 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | Chain API responded normally | 111 ms | Erlaubt |
Account Query
Gesundaccount-query responded normally
- Geprüft
- Latenz
- 375 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 | 375 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 347 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 350 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 367 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 350 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 873 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 389 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 358 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 449 ms | Erlaubt | |
| Gesund | Spring v1.2.3-alpha1 | account-query responded normally | 369 ms | Erlaubt |
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
- 328 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. | 328 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. | 112 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. | 111 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. | 115 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. | 112 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. | 113 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 | |
| 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. | 113 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. | 105 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. | 318 ms | 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
- 318 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. | 318 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. | 327 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. | 339 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. | 365 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. | 342 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. | 317 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. | 109 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. | 111 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 |