# Full Hive API Node Update - (07/01/2026) 2026-01-07T11:00:11 (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](https://github.com/thecrazygm/benchmarks). ## 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). |node | error | | --- | --- | | | NumRetriesReached | | | NumRetriesReached | | | NumRetriesReached | | | Client returned invalid format. Expected JSON! | | | NumRetriesReached | | | Received an invalid response from the endpoint. | ## 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. |node | mean time [s] | version | | --- | --- | --- | | | 0.01 | 1.28.3 | | | 0.04 | 1.28.3 | | | 0.04 | 1.28.3 | | | 0.05 | 1.28.3 | | | 0.1 | 1.28.0 | | | 0.14 | 1.28.3 | | | 0.22 | 1.28.3 | ## Node Uptime Statistics (7-day period) This table shows how reliable nodes have been over the past week. | node | uptime % | total checks | | --- | --- | --- | | | 99.41% | 169 | | | 99.41% | 169 | | | 90.32% | 186 | | | 74.34% | 226 | | | 50.6% | 332 | | | 50.15% | 335 | | | 50.0% | 336 | | | 50.0% | 336 | | | 50.0% | 336 | | | 50.0% | 336 | | | 0% | 0 | | | 0% | 0 | | | 0% | 0 | | | 0% | 0 | | | 0% | 0 | | | 0% | 0 | ## 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. | node | blocks streamed | blocks per second | | --- | --- | --- | | | 561 | 18.67 | | | 551 | 18.33 | | | 193 | 6.4 | | | 121 | 4.03 | | | 73 | 2.42 | ## 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. | node | operations streamed | operations per second | | --- | --- | --- | | | 9299 | 346.2 | | | 9299 | 866.64 | | | 9299 | 398.07 | | | 6801 | 224.75 | | | 3300 | 107.21 | | | 1201 | 38.84 | ## 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. | node | response time [s] | | --- | --- | | | 0.08 | | | 0.1 | | | 0.12 | | | 0.16 | | | 0.26 | | | 0.27 | | | 0.64 | ## 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 | blocks behind | head blocks behind irreversible | | --- | --- | --- | | | 0 | 0 | | | 0 | 0 | | | 0 | 0 | | | 1 | 0 | | | 1 | 0 | | | 1 | 0 | | | 1 | 0 | ## Node Performance Trends (7-day period) This table shows how node performance has changed over the past week. | node | block trend | history trend | API call trend | config trend | block diff trend | | --- | --- | --- | --- | --- | --- | | | ✗ failing | ✗ failing | ✗ failing | ✗ failing | ✗ failing | | | ↗ improving | n/a | ✓ stable | ↗ improving | ↗ improving | | | ✓ stable | ✓ stable | ↗ improving | ✓ stable | n/a | | | ✗ failing | ↗ improving | ✓ stable | n/a | ↗ improving | | | ✓ stable | n/a | n/a | ✓ stable | n/a | | | ✗ failing | ✗ failing | ✗ failing | ✗ failing | ✗ failing | | | ✗ failing | ✗ failing | ✗ failing | ✗ failing | ✗ failing | | | n/a | n/a | ✓ stable | ↗ improving | ✓ stable | | | n/a | ✓ stable | ✓ stable | ↗ improving | ✓ stable | | | ✓ stable | n/a | n/a | ✓ stable | n/a | ## Node Consistency (7-day period) This table shows how consistent node performance has been. Lower values indicate more consistent performance. | node | block | history | API call | config | block diff | | --- | --- | --- | --- | --- | --- | | | 0.0 | 0.28 | 0.8 | 0.3 | 0.92 | | | 0.49 | 0.53 | 0.55 | 0.66 | 0.77 | | | 0.67 | 0.51 | 0.47 | 0.39 | 1.0 | | | 0.62 | 0.21 | 0.73 | 0.24 | 1.35 | | | 0.46 | 0.51 | 0.47 | 0.5 | 1.4 | | | 0.0 | 0.36 | 0.51 | 0.8 | 1.09 | | | 0.72 | 0.89 | 0.51 | 0.3 | 1.65 | | | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | | | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | | | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | ## Overall Node Ranking This table shows an overall ranking of nodes based on their performance across all tests. | node | score | block rank | history rank | API call rank | config rank | block diff rank | | --- | --- | --- | --- | --- | --- | --- | | | 43.75 | n/a | 2 | 1 | 1 | 1 | | | 43.2 | 1 | 3 | 4 | 3 | 3 | | | 38.75 | 2 | n/a | 3 | 2 | 2 | | | 36.25 | n/a | 1 | 2 | 4 | 4 | | | 28.8 | 5 | 5 | 5 | 5 | 6 | | | 27.6 | 4 | 4 | 7 | 7 | 5 | | | 26.4 | 3 | 6 | 6 | 6 | 7 | | | 0.0 | n/a | n/a | n/a | n/a | n/a | | | 0.0 | n/a | n/a | n/a | n/a | n/a | | | 0.0 | n/a | n/a | n/a | n/a | n/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.

Author	Posts	Comments	Total Removed
@intro.bot	0	35	$6.69
@murtazataza	0	2	$0.25
@ratna675	1	0	$0.13
@haejinfans	4	0	$0.51
@dreamants	1	0	$0.13
@netscape101	2	2	$0.51
@riya.sharma	18	0	$2.29

Daily Flag Report (2018-07-25)

The accounts below have been flagged for spamming, scamming, or other shameful behavior.

Total amount of rewards returned to the reward pool in the past 24 hours by @abusereports:

$10.51

Incidents