Hive Benchmark Report - 2026-04-01

in #hivelast month

Full Hive API Node Update - (01/04/2026)

2026-04-01T11:00:09 (UTC)
Benchmarks are performed from a Digital Ocean Droplet in Frankfurt, Germany. Results may vary based on geographic location.

@nectarflower provides daily updates about the state of all available full API node servers for Hive.
More information about nectarflower can be found in the github repository.

List of failing nodes

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).

nodeerror
https://hive-api.dlux.ioNumRetriesReached
https://anyx.ioNumRetriesReached
https://hive-api.arcange.euNumRetriesReached
https://hiveapi.actifit.ioUnable to parse endpoint data.
https://api.openhive.networkClient returned invalid format. Expected JSON!
https://rpc.mahdiyari.infoClient returned invalid format. Expected JSON!

List of working nodes (At least once)

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.

nodemean time [s]version
https://hiveapi.actifit.io0.011.28.6
https://api.openhive.network0.041.28.3
https://api.c0ff33a.uk0.051.28.3
https://rpc.mahdiyari.info0.061.28.3
https://api.hive.blog / https://api.hive.blog
0.111.28.0
https://api.syncad.com0.161.28.6
https://techcoderx.com0.21.28.3

Node Uptime Statistics (7-day period)

This table shows how reliable nodes have been over the past week.

Streaming blocks

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.

nodeblocks streamedblocks per second
https://api.c0ff33a.uk52917.62
https://api.syncad.com2157.16
https://techcoderx.com1324.37
https://api.hive.blog / https://api.hive.blog
692.28

Streaming account history

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.

nodeoperations streamedoperations per second
https://api.c0ff33a.uk11632883.89
https://api.openhive.network9716323.87
https://rpc.mahdiyari.info7801258.74
https://techcoderx.com5301175.88
https://api.syncad.com4901160.01
https://api.hive.blog / https://api.hive.blog
3200103.76

API call time

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.

noderesponse time [s]
https://api.openhive.network0.12
https://api.c0ff33a.uk0.19
https://rpc.mahdiyari.info0.19
https://api.syncad.com0.27
https://techcoderx.com0.41
https://api.hive.blog / https://api.hive.blog
0.69

Block difference

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.

nodeblocks behindhead blocks behind irreversible
https://hiveapi.actifit.io00
https://api.c0ff33a.uk00
https://rpc.mahdiyari.info00
https://api.openhive.network00
https://techcoderx.com00
https://api.hive.blog / https://api.hive.blog
00
https://api.syncad.com00

Node Performance Trends (7-day period)

This table shows how node performance has changed over the past week.

nodeblock trendhistory trendAPI call trendconfig trendblock diff trend
https://anyx.io✗ failing✗ failing✗ failing✗ failing✗ failing
https://api.c0ff33a.uk↗ improving✓ stable✓ stable✓ stable✓ stable
https://api.hive.blog / https://api.hive.blog
✓ stable✓ stablen/a✓ stable↗ improving
https://api.openhive.network✗ failing✓ stable✓ stable↗ improving✓ stable
https://api.syncad.com✓ stable✓ stable↗ improving✓ stablen/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✗ failing✗ failing✗ failing✓ stable✓ stable
https://rpc.mahdiyari.info✓ stable✓ stable✓ stablen/a✓ stable
https://techcoderx.com✓ stable✓ stable↗ improving✓ stable✓ stable

Node Consistency (7-day period)

This table shows how consistent node performance has been. Lower values indicate more consistent performance.

nodeblockhistoryAPI callconfigblock diff
https://hiveapi.actifit.io0.00.00.00.390.59
https://api.openhive.network0.00.510.110.880.86
https://rpc.mahdiyari.info0.440.50.730.730.67
https://api.c0ff33a.uk0.490.170.620.711.21
https://api.syncad.com0.580.510.60.321.46
https://techcoderx.com0.790.740.620.41.04
https://api.hive.blog / https://api.hive.blog
0.730.551.10.241.08
https://hive-api.dlux.io0.00.00.00.00.0
https://hive-api.arcange.eu0.00.00.00.00.0
https://anyx.io0.00.00.00.00.0

Overall Node Ranking

This table shows an overall ranking of nodes based on their performance across all tests.

nodescoreblock rankhistory rankAPI call rankconfig rankblock diff rank
https://api.c0ff33a.uk46.811333
https://api.openhive.network38.75n/a2124
https://rpc.mahdiyari.info36.25n/a3242
https://api.syncad.com31.225467
https://techcoderx.com31.234575
https://api.hive.blog / https://api.hive.blog
27.646656
https://hiveapi.actifit.io27.0n/an/an/a11
https://hive-api.dlux.io0.0n/an/an/an/an/a
https://anyx.io0.0n/an/an/an/an/a
https://hive-api.arcange.eu0.0n/an/an/an/an/a

Conclusion

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 @nectarflower account's json_metadata for automated processing.


Generated by the hive-bench tool.