Injective Testnet
Native token
INJ
Source: DIA editorial list, from docs.injective.network.Endpoints
1 of 1
Source: DIA probe, every six hours. Counts endpoints with a check in the last 24 hours.responding
Median latency
123 ms
Source: Median round trip of the identity call over responding endpoints, from DIA's probe in Nuremberg, Germany.from one probe location
Faucets
3 listed
Source: Faucet pages DIA lists for this network.Last check
Source: The newest check on this network's endpoints and faucets.Endpoints
1 public endpoint listed. 1 of 1 checked responded in the last 24h, median 123 ms from DIA's probe in Nuremberg, Germany.
1 endpoint listed · DIA probe,
| Endpoint | Provider | Status | Latency |
|---|---|---|---|
https://testnet.sentry.tm.injective.network:443 | injective.networkOfficial | Responding | 123 ms |
Faucets
Pages that give out test tokens. A check loads the page; DIA does not request tokens, so a faucet that responds may still be empty.
3 faucets listed · DIA probe
| Faucet | Provider | Status |
|---|---|---|
| Circle Faucet (testnet USDC) | Circle | Site responds |
| Google Cloud Web3 Faucet (Injective testnet) | google.com | Site responds |
| Injective Testnet Faucet | injective.network | Site responds |
Sources and method
- Network identifier (CAIP-2):
cosmos:injective-888 - Identity listed from docs.injective.network, reviewed 20 Oct 2026.
DIA's probe sends up to two read-only requests to each listed endpoint, every six hours, from Nuremberg, Germany. Listed endpoints have answered at least once, or cannot be checked yet. One shows as Down only after four failed checks in a row, and the ones the probe cannot check read "Not checked". Read the full method.