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

in #hive5 months ago

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

2025-05-04T11:00:05 (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.roelandp.nlUnexpected response format: {'message': 'Internal Server Error'}
https://rpc.ausbit.devNumRetriesReached
https://rpc.mahdiyari.infoNumRetriesReached
https://hived.emre.shNumRetriesReached
https://api.hive.blueNumRetriesReached
https://api.openhive.networkClient 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://hive-api.3speak.tv0.011.27.5
https://hive-api.dlux.io0.011.27.8
https://api.deathwing.me0.031.27.5
https://api.openhive.network0.031.27.8
https://api.c0ff33a.uk0.051.27.5
https://hiveapi.actifit.io0.051.27.8
https://hive-api.arcange.eu0.061.27.5
https://anyx.io0.091.27.4
https://api.syncad.com0.111.27.10
https://api.hive.blog / https://api.hive.blog
0.121.27.10
https://techcoderx.com0.191.27.11

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://hive-api.3speak.tv87129.0
https://hive-api.dlux.io50916.96
https://api.c0ff33a.uk35811.91
https://api.deathwing.me33611.2
https://hiveapi.actifit.io31210.38
https://hive-api.arcange.eu2387.93
https://api.hive.blog / https://api.hive.blog
1394.62
https://techcoderx.com842.8
https://api.syncad.com792.63
https://anyx.io591.79

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.blog / https://api.hive.blog
2351308.53
https://hive-api.3speak.tv2350815.97
https://api.deathwing.me2350656.42
https://api.openhive.network2350354.45
https://hive-api.arcange.eu2350403.09
https://hive-api.dlux.io2350925.2
https://api.c0ff33a.uk2350681.16
https://hiveapi.actifit.io2350610.39
https://api.syncad.com2350117.62
https://anyx.io2350248.41
https://techcoderx.com2350185.92

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.

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.

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.ion/an/a✗ failing↗ improvingn/a
https://api.c0ff33a.uk↗ improvingn/a↗ improvingn/a↗ improving
https://api.deathwing.men/an/a✓ stable↗ improving↗ improving
https://api.hive.blog / https://api.hive.blog
✓ stable✓ stable✓ stablen/an/a
https://api.hive.blue✓ stable✓ stablen/an/an/a
https://api.openhive.network✗ failing↗ improving✓ stable↗ improving↗ improving
https://api.syncad.com✓ stable↗ improving✓ stable✓ stablen/a
https://hive-api.3speak.tv✓ stable↗ improving✓ stable↗ improving✓ stable
https://hive-api.arcange.eun/a↗ improvingn/a✓ stablen/a
https://hive-api.dlux.io✓ stablen/a✓ stablen/a↗ improving
https://hive.roelandp.nl✗ failing✗ failing↗ improving✓ stable✓ stable
https://hiveapi.actifit.ion/an/a✓ stablen/an/a
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✓ stablen/an/a✓ 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://hive-api.3speak.tv0.260.90.21.031.52
https://hive-api.dlux.io0.171.080.560.662.61
https://techcoderx.com0.690.920.090.393.01
https://hive-api.arcange.eu0.541.020.850.632.1
https://hiveapi.actifit.io0.720.930.331.02.19
https://api.syncad.com0.851.220.290.782.67
https://api.c0ff33a.uk0.751.090.791.042.14
https://api.hive.blog / https://api.hive.blog
0.71.20.370.823.09
https://api.deathwing.me0.760.780.591.352.88
https://anyx.io0.920.580.00.922.93
https://api.hive.blue0.470.410.00.723.93
https://api.openhive.network0.01.20.91.822.33
https://hive.roelandp.nl0.00.00.490.583.83
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.me42.043233
https://hive-api.dlux.io42.026322
https://api.c0ff33a.uk30.037555
https://hive-api.arcange.eu26.465674
https://hiveapi.actifit.io24.058467
https://api.openhive.network23.75n/a4746
https://api.hive.blog / https://api.hive.blog
16.87181010
https://api.syncad.com6.099999
https://api.hive.blue4.0n/an/an/an/a8
https://anyx.io2.01010n/a813
https://techcoderx.com2.0811111111
https://hive.roelandp.nl0.0n/an/a10n/a12
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 account's json_metadata for automated processing.


Generated by the hive-bench tool.

Sort:  

Congratulations @nectarflower! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You published more than 60 posts.
Your next target is to reach 70 posts.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out our last posts:

Our Hive Power Delegations to the April PUM Winners
Feedback from the May Hive Power Up Day
Hive Power Up Month Challenge - April 2025 Winners List