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

in #hive • 9 months ago

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

2025-04-23T11:00:03 (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://hived.emre.shNumRetriesReached
https://rpc.mahdiyari.infoNumRetriesReached
https://api.hive.blueNumRetriesReached
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.dlux.io0.011.27.8
https://api.deathwing.me0.031.27.5
https://hive-api.3speak.tv0.041.27.5
https://api.openhive.network0.041.27.8
https://hiveapi.actifit.io0.041.27.8
https://api.c0ff33a.uk0.041.27.5
https://hive-api.arcange.eu0.071.27.5
https://anyx.io0.111.27.4
https://api.syncad.com0.131.27.10
https://api.hive.blog / https://api.hive.blog
0.151.27.8
https://techcoderx.com0.191.27.7

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%114
https://api.deathwing.me100.0%114
https://api.hive.blog / https://api.hive.blog
100.0%114
https://hiveapi.actifit.io100.0%114
https://api.syncad.com99.13%115
https://techcoderx.com99.13%115
https://hive-api.arcange.eu94.21%121
https://anyx.io91.94%124
https://hive-api.3speak.tv75.5%151
https://hive-api.dlux.io64.41%177
https://rpc.mahdiyari.info53.77%212
https://api.hive.blue50.0%228
https://api.openhive.network50.0%228
https://hive.roelandp.nl50.0%228
https://hived.emre.sh50.0%228
https://rpc.ausbit.dev50.0%228

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.tv85728.56
https://api.deathwing.me61220.39
https://hiveapi.actifit.io49416.44
https://api.c0ff33a.uk43214.39
https://hive-api.arcange.eu32710.89
https://api.hive.blog / https://api.hive.blog
1886.26
https://api.syncad.com1816.02
https://anyx.io1705.66
https://techcoderx.com1133.76

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
1582311.42
https://hive-api.3speak.tv1581883.24
https://api.deathwing.me1581687.39
https://hive-api.dlux.io15811007.01
https://api.openhive.network1581392.31
https://hiveapi.actifit.io1581605.75
https://api.c0ff33a.uk1581482.01
https://hive-api.arcange.eu1581629.88
https://api.syncad.com1581115.49
https://techcoderx.com1581246.26
https://anyx.io1581257.07

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://hive-api.dlux.io0.07
https://hiveapi.actifit.io0.1
https://api.c0ff33a.uk0.14
https://hive-api.arcange.eu0.16
https://api.openhive.network0.19
https://api.hive.blog / https://api.hive.blog
0.23
https://api.syncad.com0.25
https://techcoderx.com0.41

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://techcoderx.com00
https://hive.roelandp.nl00
https://hive-api.3speak.tv20
https://hive-api.dlux.io20
https://api.deathwing.me20
https://hive-api.arcange.eu20
https://api.openhive.network20
https://api.c0ff33a.uk20
https://hiveapi.actifit.io20
https://api.syncad.com20
https://api.hive.blog / https://api.hive.blog
30
https://anyx.io50

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✓ stablen/a✗ failing↗ improvingn/a
https://api.c0ff33a.uk✓ stable✓ stable↗ improving✓ stable✓ stable
https://api.deathwing.me✓ stable✓ stable↗ improving↗ improvingn/a
https://api.hive.blog / https://api.hive.blog
↗ improving✓ stable✓ stable✓ stable✓ stable
https://api.hive.blue↗ improving↗ improving✗ failing↗ improving✓ stable
https://api.openhive.network✗ failing✓ stable✓ stablen/an/a
https://api.syncad.com↗ improving↗ improving✓ stable↗ improving✓ stable
https://hive-api.3speak.tv✓ stable✓ stable✓ stablen/an/a
https://hive-api.arcange.eu↗ improving✓ stable↗ improving↗ improvingn/a
https://hive-api.dlux.ion/a✓ stablen/a✓ stablen/a
https://hive.roelandp.nl↗ improving✓ stable↗ improvingn/a↗ improving
https://hiveapi.actifit.io✓ stable↗ improving↗ improving↗ 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✓ stable↗ improvingn/a
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.01.120.211.091.85
https://hiveapi.actifit.io0.951.030.41.072.1
https://hive-api.dlux.io0.331.360.570.772.55
https://hive-api.arcange.eu0.841.190.930.771.87
https://api.c0ff33a.uk1.030.950.831.122.1
https://techcoderx.com0.890.560.480.673.45
https://api.syncad.com1.141.120.481.062.95
https://anyx.io1.20.780.00.72.79
https://api.hive.blog / https://api.hive.blog
0.960.00.510.93.31
https://api.deathwing.me1.090.820.851.562.81
https://hive.roelandp.nl1.220.00.380.693.69
https://api.openhive.network0.01.161.122.052.27
https://api.hive.blue1.640.380.00.824.24
https://rpc.mahdiyari.info1.152.861.261.213.32
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.tv48.012133
https://api.deathwing.me43.223225
https://hive-api.dlux.io35.0n/a4314
https://hiveapi.actifit.io27.636459
https://api.c0ff33a.uk24.047568
https://hive-api.arcange.eu21.658676
https://api.openhive.network21.25n/a5747
https://api.hive.blog / https://api.hive.blog
17.86181011
https://hive.roelandp.nl16.0n/an/an/an/a2
https://techcoderx.com11.891010111
https://api.syncad.com7.2799910
https://anyx.io4.25811n/a812
https://rpc.ausbit.dev0.0n/an/an/an/an/a
https://hived.emre.sh0.0n/an/an/an/an/a
https://rpc.mahdiyari.info0.0n/an/an/an/an/a
https://api.hive.blue0.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
9 months ago in #hive by
$0.10
  • Past Payouts $0.10
  • - Author $0.05
  • - Curators $0.05
11 votes
Reply 1
Sort:  
  • Trending
    • [-]
     9 months ago  

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

    You received more than 500 upvotes.
    Your next target is to reach 600 upvotes.

    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

    $0.00
      Reply