Fuel, Kusama, HECO, Kinto and 0G Galileo endpoints retired
We retired the HECO and Kinto endpoints on Ankr RPC on 13 October 2026, as neither serves chain data any more. They join the Fuel, Kusama and 0G Galileo testnet endpoints we retired on 15 September 2026, as announced. The API reference pages for HECO, Kinto, Fuel and Kusama and their entries in the chain list are gone. No method limits, error codes or rate limits changed on any other network.
Deprecations and end-of-support
| Network | Endpoints retired | Date |
|---|---|---|
| Fuel | mainnet fuel and Sepolia testnet fuel_sepolia | 15 September 2026 |
| Kusama | mainnet kusama | 15 September 2026 |
| 0G | Galileo testnet 0g_galileo_testnet_evm, 0g_galileo_testnet_tendermint and 0g_galileo_testnet_beaconkit | 15 September 2026 |
| HECO | mainnet heco | 13 October 2026 |
| Kinto | mainnet kinto | 13 October 2026 |
0G mainnet EVM and mainnet BeaconKit stay, with the same URLs, plan and rate limits. Inbound links to the removed HECO, Kinto, Fuel and Kusama pages resolve to the chain list instead of returning a 404.
Worth checking on your side
- Search your configuration for the endpoint strings in the table, not the network name. They appear on
rpc.ankr.comon their own, after/premium-http/, or in the keyless form/http/<name>. - A call with an API key to a retired endpoint answers
-32055 No nodes available. Elsewhere that code is transient, so a client with retry logic keeps retrying here. A call without a key answers-32052, which reads like an access problem but is not one: the endpoint is gone. In both cases, remove it from your configuration. - Fuel runs its own public GraphQL endpoints that speak the same API:
https://mainnet.fuel.network/v1/graphqlandhttps://testnet.fuel.network/v1/graphql. See the Fuel documentation for their limits.