Hive Benchmark Report - 2025-05-28

in #hive • 9 days ago

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

2025-05-28T11:00:06 (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://api.hive.blueNumRetriesReached
https://rpc.ausbit.devNumRetriesReached
https://hived.emre.shNumRetriesReached
https://hive.roelandp.nlUnexpected response format: {'message': 'Internal Server Error'}
https://api.openhive.networkClient returned invalid format. Expected JSON!
https://hive-api.dlux.ioNumRetriesReached

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.051.27.5
https://hive-api.dlux.io0.081.27.8
https://hiveapi.actifit.io0.081.27.11
https://anyx.io0.111.27.4
https://api.hive.blog / https://api.hive.blog
0.111.27.11
https://api.openhive.network0.121.27.8
https://rpc.mahdiyari.info0.121.27.10
https://api.deathwing.me0.211.27.5
https://techcoderx.com0.211.27.11
https://api.c0ff33a.uk0.221.27.5
https://hive-api.arcange.eu0.231.27.5
https://hive.roelandp.nl0.351.27.4
https://api.syncad.com0.521.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.blog / https://api.hive.blog
100.0%168
https://api.syncad.com100.0%168
https://hive-api.arcange.eu100.0%168
https://rpc.mahdiyari.info100.0%168
https://hiveapi.actifit.io99.41%169
https://techcoderx.com99.41%169
https://hive-api.3speak.tv98.25%171
https://anyx.io88.42%190
https://hive-api.dlux.io53.85%312
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

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.tv87228.8
https://rpc.mahdiyari.info46615.52
https://api.deathwing.me43914.61
https://api.c0ff33a.uk38912.96
https://hiveapi.actifit.io36912.29
https://hive-api.arcange.eu2648.79
https://api.hive.blog / https://api.hive.blog
1344.45
https://anyx.io1133.76
https://techcoderx.com601.99
https://api.syncad.com571.9

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
3456237.85
https://hive-api.3speak.tv3455537.33
https://hive-api.dlux.io3455605.08
https://hiveapi.actifit.io3455521.9
https://anyx.io3455226.85
https://api.openhive.network3455291.32
https://rpc.mahdiyari.info3455440.13
https://api.deathwing.me3455451.04
https://techcoderx.com3455232.82
https://api.c0ff33a.uk3455475.9
https://hive-api.arcange.eu3455443.52
https://api.syncad.com260186.38

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.04
https://rpc.mahdiyari.info0.07
https://hive-api.dlux.io0.08
https://hiveapi.actifit.io0.09
https://api.deathwing.me0.09
https://api.c0ff33a.uk0.15
https://hive-api.arcange.eu0.16
https://api.hive.blog / https://api.hive.blog
0.2
https://api.openhive.network0.21
https://api.syncad.com0.27
https://techcoderx.com0.39

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.deathwing.me00
https://hive-api.3speak.tv00
https://hive-api.dlux.io00
https://hive-api.arcange.eu00
https://rpc.mahdiyari.info00
https://api.openhive.network00
https://api.c0ff33a.uk00
https://hiveapi.actifit.io00
https://api.syncad.com10
https://api.hive.blog / https://api.hive.blog
10
https://techcoderx.com10
https://hive.roelandp.nl10
https://anyx.io60

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/a↗ improving✗ failing↗ improvingn/a
https://api.c0ff33a.uk✓ stablen/a↗ improvingn/a✓ stable
https://api.deathwing.men/an/an/a✓ stable↗ improving
https://api.hive.blog / https://api.hive.blog
↗ improving✓ stable✓ stable↗ improvingn/a
https://api.hive.blue✗ failing✗ failing✗ failing✗ failing✗ failing
https://api.openhive.network✗ failing✓ stablen/an/an/a
https://api.syncad.comn/an/an/a✓ stablen/a
https://hive-api.3speak.tv✓ stable↗ improving✓ stable↗ improvingn/a
https://hive-api.arcange.eu✓ stablen/an/an/a↗ improving
https://hive-api.dlux.ion/a↗ improving✓ stablen/an/a
https://hive.roelandp.nl✗ failing✗ failing✓ stable✓ stable↗ improving
https://hiveapi.actifit.io✓ stable↗ improving✓ stable↗ improvingn/a
https://hived.emre.sh✗ failing✗ failing✗ failing✗ failing✗ failing
https://rpc.ausbit.dev✗ failing✗ failing✗ failing✗ failing✗ failing
https://rpc.mahdiyari.info↗ improving↗ improving↗ improvingn/an/a
https://techcoderx.com↗ improving✓ stablen/a↗ improvingn/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.640.580.240.561.77
https://hive-api.3speak.tv0.250.730.151.591.34
https://api.syncad.com0.850.70.370.71.82
https://hive-api.arcange.eu0.371.090.721.021.67
https://hiveapi.actifit.io0.660.920.441.151.74
https://rpc.mahdiyari.info0.740.940.861.561.1
https://api.c0ff33a.uk0.650.960.621.271.8
https://api.hive.blog / https://api.hive.blog
0.660.980.451.062.26
https://hive-api.dlux.io0.381.040.841.462.4
https://anyx.io0.90.580.00.932.75
https://hive.roelandp.nl0.00.00.120.523.62
https://api.deathwing.me0.780.980.91.752.88
https://api.openhive.network0.01.791.12.52.04
https://api.hive.blue0.00.00.00.00.0
https://rpc.ausbit.dev0.00.00.00.00.0
https://hived.emre.sh0.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.tv51.612112
https://hive-api.dlux.io35.0n/a4323
https://api.deathwing.me34.835481
https://rpc.mahdiyari.info33.626275
https://hiveapi.actifit.io26.457538
https://api.hive.blog / https://api.hive.blog
22.8718510
https://api.openhive.network20.0n/a3966
https://hive-api.arcange.eu17.8687114
https://api.c0ff33a.uk16.8496107
https://anyx.io9.25810n/a413
https://techcoderx.com2.091111911
https://api.syncad.com1.0101210139
https://hive.roelandp.nl0.0n/an/an/a1212
https://api.hive.blue0.0n/an/an/an/an/a
https://rpc.ausbit.dev0.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.

#benchmark #nodes #performance #api #sbi-skip
9 days ago in #hive by
$0.00
    Reply 0
    Sort:  
  • Trending