2026-06-03T11:00:10 (UTC)
Benchmarks are performed from a Digital Ocean Droplet in Frankfurt, Germany. Results may vary based on geographic location.
More information about nectarflower can be found in the github repository.
This table includes a list of all nodes which were not able to answer to a get_config API call within the specified timeout (default: 60 seconds).
| node | error |
|---|---|
| https://hive-api.dlux.io | NumRetriesReached |
| https://anyx.io | NumRetriesReached |
| https://hive-api.arcange.eu | NumRetriesReached |
| https://api.openhive.network | Client returned invalid format. Expected JSON! |
| https://hiveapi.actifit.io | Unable to parse endpoint data. |
This table includes all nodes which were able to answer a get_config call within the timeout (default: 60 seconds). The achieved mean duration values are shown. The returned version is also shown.
| node | mean time [s] | version |
|---|---|---|
| https://hiveapi.actifit.io | 0.02 | 1.28.6 |
| https://api.openhive.network | 0.04 | 1.28.3 |
| https://api.c0ff33a.uk | 0.05 | 1.28.3 |
| https://rpc.mahdiyari.info | 0.06 | 1.28.3 |
| https://api.hive.blog | 0.09 | 1.28.6 |
| https://api.syncad.com | 0.15 | 1.28.6 |
| https://techcoderx.com | 0.18 | 1.28.6 |
This table shows how reliable nodes have been over the past week.
| node | uptime % | total checks |
|---|---|---|
| https://api.hive.blog | 100.0% | 168 |
| https://rpc.mahdiyari.info | 100.0% | 168 |
| https://techcoderx.com | 100.0% | 168 |
| https://api.c0ff33a.uk | 98.82% | 170 |
| https://api.syncad.com | 79.62% | 211 |
| https://hiveapi.actifit.io | 50.91% | 330 |
| https://api.openhive.network | 50.15% | 335 |
| https://anyx.io | 50.0% | 336 |
| https://hive-api.arcange.eu | 50.0% | 336 |
| https://hive-api.dlux.io | 50.0% | 336 |
| https://api.deathwing.me | 0% | 0 |
| https://api.hive.blue | 0% | 0 |
| https://hive-api.3speak.tv | 0% | 0 |
| https://hive.roelandp.nl | 0% | 0 |
| https://hived.emre.sh | 0% | 0 |
| https://rpc.ausbit.dev | 0% | 0 |
This table shows how many blocks were streamed by the node within the default benchmark duration (30 seconds). The RPCs are ordered according to the number of blocks streamed.
| node | blocks streamed | blocks per second |
|---|---|---|
| https://api.c0ff33a.uk | 492 | 16.38 |
| https://rpc.mahdiyari.info | 372 | 12.39 |
| https://hiveapi.actifit.io | 336 | 11.17 |
| https://api.hive.blog | 248 | 8.25 |
| https://techcoderx.com | 135 | 4.49 |
| https://api.syncad.com | 112 | 3.73 |
This table shows how many account history operations were streamed by the node within the default benchmark duration (60 seconds). The RPCs are ordered according to the number of operations streamed.
| node | operations streamed | operations per second |
|---|---|---|
| https://api.c0ff33a.uk | 13416 | 666.14 |
| https://api.openhive.network | 8701 | 287.35 |
| https://rpc.mahdiyari.info | 8401 | 279.1 |
| https://api.hive.blog | 7900 | 261.94 |
| https://techcoderx.com | 7501 | 247.8 |
| https://api.syncad.com | 3901 | 129.26 |
| https://hiveapi.actifit.io | 2501 | 82.92 |
This table shows how long it took to call an API (single request, default timeout: 60 seconds). The RPCs are ordered according to the access time.
| node | response time [s] |
|---|---|
| https://api.openhive.network | 0.09 |
| https://api.c0ff33a.uk | 0.16 |
| https://rpc.mahdiyari.info | 0.16 |
| https://api.syncad.com | 0.29 |
| https://api.hive.blog | 0.34 |
| https://techcoderx.com | 0.44 |
This table shows the head blocks reported by each node. By comparing with the highest one, we can tell if a node has issues with block processing.
| node | blocks behind | head blocks behind irreversible |
|---|---|---|
| https://hiveapi.actifit.io | 0 | 0 |
| https://rpc.mahdiyari.info | 0 | 0 |
| https://api.c0ff33a.uk | 0 | 0 |
| https://api.openhive.network | 0 | 0 |
| https://techcoderx.com | 0 | 0 |
| https://api.hive.blog | 1 | 0 |
| https://api.syncad.com | 1 | 0 |
This table shows how node performance has changed over the past week.
| node | block trend | history trend | API call trend | config trend | block diff trend |
|---|---|---|---|---|---|
| https://anyx.io | ✗ failing | ✗ failing | ✗ failing | ✗ failing | ✗ failing |
| https://api.c0ff33a.uk | ✓ stable | ↗ improving | ↗ improving | ✓ stable | ↗ improving |
| https://api.hive.blog | n/a | ↗ improving | ↗ improving | ✓ stable | n/a |
| https://api.openhive.network | n/a | ↗ improving | ↗ improving | ↗ improving | ↗ improving |
| https://api.syncad.com | n/a | ↗ improving | ↗ improving | ✓ stable | n/a |
| https://hive-api.arcange.eu | ✗ failing | ✗ failing | ✗ failing | ✗ failing | ✗ failing |
| https://hive-api.dlux.io | ✗ failing | ✗ failing | ✗ failing | ✗ failing | ✗ failing |
| https://hiveapi.actifit.io | n/a | n/a | n/a | ✓ stable | ↗ improving |
| https://rpc.mahdiyari.info | ✓ stable | ↗ improving | ↗ improving | n/a | ↗ improving |
| https://techcoderx.com | ✓ stable | n/a | ↗ improving | ✓ stable | ↗ improving |
This table shows how consistent node performance has been. Lower values indicate more consistent performance.
| node | block | history | API call | config | block diff |
|---|---|---|---|---|---|
| https://api.c0ff33a.uk | 0.25 | 0.41 | 0.76 | 0.79 | 1.2 |
| https://api.hive.blog | 0.55 | 0.97 | 0.95 | 0.4 | 0.94 |
| https://techcoderx.com | 0.7 | 1.34 | 0.68 | 0.53 | 0.68 |
| https://api.syncad.com | 0.77 | 0.68 | 0.83 | 0.48 | 1.69 |
| https://api.openhive.network | 0.0 | 1.21 | 0.67 | 1.07 | 0.75 |
| https://rpc.mahdiyari.info | 0.92 | 1.41 | 0.88 | 0.98 | 0.71 |
| https://hiveapi.actifit.io | 1.69 | 2.32 | 1.22 | 0.52 | 0.47 |
| https://hive-api.dlux.io | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| https://anyx.io | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| https://hive-api.arcange.eu | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
This table shows an overall ranking of nodes based on their performance across all tests.
| node | score | block rank | history rank | API call rank | config rank | block diff rank |
|---|---|---|---|---|---|---|
| https://api.c0ff33a.uk | 46.8 | 1 | 1 | 3 | 3 | 3 |
| https://rpc.mahdiyari.info | 44.4 | 2 | 3 | 2 | 4 | 2 |
| https://api.openhive.network | 38.75 | n/a | 2 | 1 | 2 | 4 |
| https://hiveapi.actifit.io | 35.0 | 3 | 7 | n/a | 1 | 1 |
| https://api.hive.blog | 31.2 | 4 | 4 | 5 | 5 | 6 |
| https://techcoderx.com | 26.4 | 5 | 5 | 6 | 7 | 5 |
| https://api.syncad.com | 25.2 | 6 | 6 | 4 | 6 | 7 |
| https://hive-api.dlux.io | 0.0 | n/a | n/a | n/a | n/a | n/a |
| https://anyx.io | 0.0 | n/a | n/a | n/a | n/a | n/a |
| https://hive-api.arcange.eu | 0.0 | n/a | n/a | n/a | n/a | n/a |
This report provides a snapshot of Hive node performance. Users can use this information to select reliable nodes for their applications.
The benchmark data is also available in JSON format in the json_metadata for automated processing.
Generated by the hive-bench tool.
