Historique de disponibilité
Contrôles sains et dégradés des fonctions surveillées. Les périodes sans données sont exclues.
48.8 % de disponibilité
1 an
31 oct. 2025 UTCGris : aucun contrôle enregistréMaintenant
Jungle Testnet
73e4385a2708e6d7048834fbc1079f2fabb17b3c125b146af438971e90716c4d
https://jungle.eosusa.io
Santé, fraîcheur, CORS et historique récent des contrôles pour cet endpoint.
- Producteur
- ivote4eosusa
- Chaîne
- Jungle Testnet
- Historique de chaîne déclaré
- Complet
- Emplacement
- Greenville,SC,USA
État actuel des services
Chain API
SainChain API responded normally
- Vérifié
- Latence
- 345 ms
- Requêtes du navigateur
- Autorisées
- Version
- Spring v1.2.3-alpha1
Contrôles récents
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 345 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 107 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 111 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 101 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 111 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 113 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 107 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 109 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 105 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | Chain API responded normally | 110 ms | Autorisées |
Account Query
Sainaccount-query responded normally
- Vérifié
- Latence
- 358 ms
- Requêtes du navigateur
- Autorisées
- Version
- Spring v1.2.3-alpha1
Contrôles récents
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 358 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 449 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 369 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 346 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 366 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 364 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 335 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 357 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 362 ms | Autorisées | |
| Sain | Spring v1.2.3-alpha1 | account-query responded normally | 370 ms | Autorisées |
History API
InvalideHTTP 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.
- Vérifié
- Latence
- 113 ms
- Requêtes du navigateur
- Bloquées
- 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.
Contrôles récents
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Invalide | 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 | Bloquées | |
| Invalide | 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 | Bloquées | |
| Invalide | 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 | Bloquées | |
| Invalide | 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 | Bloquées | |
| Invalide | 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. | 320 ms | Bloquées | |
| Invalide | 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 | Bloquées | |
| Invalide | 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. | 106 ms | Bloquées | |
| Invalide | 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 | Bloquées | |
| Invalide | 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 | Bloquées | |
| Invalide | 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 | Bloquées |
Hyperion API
InvalideHTTP 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.
- Vérifié
- Latence
- 114 ms
- Requêtes du navigateur
- Bloquées
- Version
- Inconnue
Response Access-Control-Allow-Origin is missing. It must be "*" or echo the request Origin, otherwise browser apps cannot read the response.
Contrôles récents
| État | Version | Résumé | Latence | CORS | Vérifié |
|---|---|---|---|---|---|
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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. | 104 ms | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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. | 332 ms | Bloquées | |
| Invalide | Inconnue | 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. | 323 ms | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées | |
| Invalide | Inconnue | 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 | Bloquées |