Hive Benchmark Report - 2025-12-10

in #hive3 days ago

Full Hive API Node Update - (10/12/2025)

2025-12-10T11:00:07 (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://hive-api.arcange.euNumRetriesReached
https://anyx.ioNumRetriesReached
https://api.openhive.networkClient returned invalid format. Expected JSON!
https://rpc.mahdiyari.infoClient returned invalid format. Expected JSON!
https://hiveapi.actifit.ioNumRetriesReached
https://techcoderx.comUnable to parse endpoint data.

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.3
https://rpc.mahdiyari.info0.041.28.3
https://api.openhive.network0.041.28.3
https://api.c0ff33a.uk0.041.28.3
https://api.hive.blog / https://api.hive.blog
0.111.28.0
https://api.syncad.com0.191.28.3
https://techcoderx.com0.191.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.uk51517.14
https://api.syncad.com1886.26
https://techcoderx.com1264.19
https://api.hive.blog / https://api.hive.blog
702.33

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://hiveapi.actifit.io8593307.99
https://rpc.mahdiyari.info8593321.35
https://api.openhive.network8593400.23
https://api.c0ff33a.uk8593868.86
https://techcoderx.com4101134.46
https://api.hive.blog / https://api.hive.blog
3113103.77
https://api.syncad.com100131.83

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://hiveapi.actifit.io0.04
https://api.openhive.network0.08
https://api.c0ff33a.uk0.13
https://rpc.mahdiyari.info0.14
https://api.hive.blog / https://api.hive.blog
0.23
https://api.syncad.com0.23

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://api.openhive.network00
https://api.syncad.com00
https://hiveapi.actifit.io20
https://api.c0ff33a.uk20
https://rpc.mahdiyari.info20
https://techcoderx.com20
https://api.hive.blog / https://api.hive.blog
30

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✗ failingn/a✓ stable
https://api.c0ff33a.uk✓ stable✓ stable✓ stable✓ stablen/a
https://api.hive.blog / https://api.hive.blog
✓ stable✓ stablen/a↗ improvingn/a
https://api.openhive.network✗ failing✓ stable✓ stablen/a↗ improving
https://api.syncad.com✓ stable✓ stable↗ improving✓ stable↗ improving
https://hive-api.arcange.eu✗ failing✗ failing✗ failing✗ failing✗ failing
https://hive-api.dlux.io✗ failing✗ failing✗ failing✗ failing✗ failing
https://hiveapi.actifit.io✗ failingn/a✓ stable✓ stablen/a
https://rpc.mahdiyari.info✓ stable↗ improving✓ stable↗ improvingn/a
https://techcoderx.com✓ stable✓ stable✓ stable✓ stablen/a

Node Consistency (7-day period)

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

nodeblockhistoryAPI callconfigblock diff
https://techcoderx.com0.50.180.250.421.02
https://anyx.io0.00.00.00.510.0
https://hiveapi.actifit.io0.00.620.440.410.62
https://rpc.mahdiyari.info0.450.760.550.710.57
https://api.c0ff33a.uk0.50.510.510.541.17
https://api.openhive.network0.00.730.340.720.99
https://api.syncad.com0.530.370.30.51.82
https://api.hive.blog / https://api.hive.blog
0.751.10.340.450.92
https://hive-api.arcange.eu0.00.00.00.00.0
https://hive-api.dlux.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.uk40.814344
https://hiveapi.actifit.io40.0n/a3113
https://api.openhive.network40.0n/a2231
https://rpc.mahdiyari.info35.0n/a1425
https://api.syncad.com33.627562
https://api.hive.blog / https://api.hive.blog
26.446657
https://techcoderx.com23.7535n/a76
https://hive-api.dlux.io0.0n/an/an/an/an/a
https://hive-api.arcange.eu0.0n/an/an/an/an/a
https://anyx.io0.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.