Full Hive API Node Update - (07/05/2025)

nectarflower(51)
Published in
#hive
Words
750
Reading
4 min
1y
Listen to this post
~5 min

Full Hive API Node Update - (07/05/2025)

2025-05-07T11:00:05 (UTC)
Benchmarks are performed from a Digital Ocean Droplet in Frankfurt, Germany. Results may vary based on geographic location.

nectarflower@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.roelandp.nlUnexpected response format: {'message': 'Internal Server Error'}
https://hive-api.dlux.ioNumRetriesReached
https://api.syncad.comNumRetriesReached
https://rpc.ausbit.devNumRetriesReached
https://rpc.mahdiyari.infoNumRetriesReached
https://hived.emre.shNumRetriesReached
https://api.openhive.networkClient returned invalid format. Expected JSON!
https://api.hive.blueUnable 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://hive-api.3speak.tv0.021.27.5
https://hiveapi.actifit.io0.041.27.8
https://api.c0ff33a.uk0.041.27.5
https://api.deathwing.me0.051.27.5
https://hive-api.arcange.eu0.071.27.5
https://api.openhive.network0.071.27.8
https://anyx.io0.11.27.4
https://api.hive.blog0.11.27.11
https://api.hive.blue0.171.27.5
https://techcoderx.com0.21.27.11

Node Uptime Statistics (7-day period)

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

nodeuptime %total checks
https://api.c0ff33a.uk100.0%168
https://api.deathwing.me100.0%168
https://api.hive.blog100.0%168
https://hive-api.arcange.eu100.0%168
https://hiveapi.actifit.io100.0%168
https://hive-api.3speak.tv97.67%172
https://api.syncad.com95.45%176
https://anyx.io88.42%190
https://techcoderx.com75.0%224
https://hive-api.dlux.io64.12%262
https://api.hive.blue50.0%336
https://api.openhive.network50.0%336
https://hive.roelandp.nl50.0%336
https://hived.emre.sh50.0%336
https://rpc.ausbit.dev50.0%336
https://rpc.mahdiyari.info50.0%336

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://hive-api.3speak.tv67022.31
https://api.c0ff33a.uk48616.19
https://api.deathwing.me43214.38
https://hiveapi.actifit.io39613.18
https://hive-api.arcange.eu2638.75
https://api.hive.blog1715.68
https://anyx.io1474.89
https://api.hive.blue1424.73
https://techcoderx.com902.99

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.hive.blog2547342.34
https://hive-api.3speak.tv2546868.94
https://hiveapi.actifit.io2546601.89
https://api.c0ff33a.uk2546731.61
https://api.deathwing.me2546668.24
https://hive-api.arcange.eu2546488.68
https://api.openhive.network2546367.39
https://anyx.io2546256.65
https://techcoderx.com2546210.94

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://hive-api.3speak.tv0.03
https://api.deathwing.me0.06
https://hiveapi.actifit.io0.09
https://api.c0ff33a.uk0.12
https://hive-api.arcange.eu0.18
https://api.openhive.network0.18
https://api.hive.blog0.24
https://hive.roelandp.nl1.52
https://techcoderx.com1.55

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://hive-api.3speak.tv00
https://api.deathwing.me00
https://api.openhive.network00
https://hive-api.arcange.eu00
https://hiveapi.actifit.io00
https://api.c0ff33a.uk00
https://api.hive.blog10
https://api.hive.blue10
https://techcoderx.com10
https://anyx.io40

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✓ stable↗ improving✗ failing✓ stablen/a
https://api.c0ff33a.uk↗ improving↗ improving↗ improving✓ stablen/a
https://api.deathwing.me✓ stable↗ improving↗ improving↗ improving↗ improving
https://api.hive.blog↗ improving✓ stable↗ improving✓ stable↗ improving
https://api.hive.blue↗ improving✓ stable✗ failing↗ improving↗ improving
https://api.openhive.network✗ failingn/a✓ stablen/a↗ improving
https://api.syncad.com✓ stablen/a✓ stable✓ stable↗ improving
https://hive-api.3speak.tv✓ stable↗ improving✓ stable↗ improving✓ stable
https://hive-api.arcange.eu↗ improving↗ improving↗ improving↗ improving↗ improving
https://hive-api.dlux.io✓ stable↗ improvingn/a✓ stablen/a
https://hive.roelandp.nl✗ failing✗ failing↗ improving↗ improving↗ improving
https://hiveapi.actifit.io↗ improving↗ improving↗ improving✓ stable↗ improving
https://hived.emre.sh✗ failing✗ failing✗ failing✗ failing✗ failing
https://rpc.ausbit.dev✗ failing✗ failing✗ failing✗ failing✗ failing
https://rpc.mahdiyari.info✗ failing✗ failing✗ failing✗ failing✗ failing
https://techcoderx.com✓ stable↗ improving↗ improving↗ improving↗ improving

Node Consistency (7-day period)

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

nodeblockhistoryAPI callconfigblock diff
https://hive-api.3speak.tv0.280.860.21.21.77
https://hive-api.dlux.io0.231.130.550.712.27
https://hive-api.arcange.eu0.540.960.880.772.06
https://hiveapi.actifit.io0.760.920.451.02.09
https://api.c0ff33a.uk0.730.970.810.92.04
https://techcoderx.com0.71.030.560.472.78
https://api.deathwing.me0.770.790.521.52.46
https://api.syncad.com0.891.410.280.792.74
https://api.hive.blog0.720.930.450.863.23
https://anyx.io0.950.640.01.022.7
https://api.openhive.network0.01.160.981.772.22
https://hive.roelandp.nl0.00.00.630.593.81
https://api.hive.blue1.340.510.01.233.84
https://rpc.ausbit.dev0.00.00.00.00.0
https://hived.emre.sh0.00.00.00.00.0
https://rpc.mahdiyari.info0.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://hive-api.3speak.tv52.812111
https://api.deathwing.me43.233242
https://hiveapi.actifit.io36.046325
https://api.c0ff33a.uk33.627436
https://hive-api.arcange.eu32.454554
https://api.hive.blog25.261787
https://api.openhive.network25.0n/a5663
https://anyx.io10.078n/a710
https://api.hive.blue6.678n/an/a98
https://techcoderx.com4.8999109
https://hive.roelandp.nl4.0n/an/a8n/an/a
https://hive-api.dlux.io0.0n/an/an/an/an/a
https://api.syncad.com0.0n/an/an/an/an/a
https://rpc.ausbit.dev0.0n/an/an/an/an/a
https://rpc.mahdiyari.info0.0n/an/an/an/an/a
https://hived.emre.sh0.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@nectarflower account's json_metadata for automated processing.

Generated by the hive-bench tool.

hive
benchmark
nodes
performance
api
via hive-bench
This post was published via hive-bench. Ecency is not the originator or editor of this content and displays it for discovery purposes only.
9