Full Hive API Node Update - (12/08/2026)

2026-08-12T11: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).

node	error
https://hive-api.dlux.io	NumRetriesReached
https://api.c0ff33a.uk	NumRetriesReached
https://anyx.io	NumRetriesReached
https://hive-api.arcange.eu	NumRetriesReached
https://api.openhive.network	NumRetriesReached
https://hiveapi.actifit.io	NumRetriesReached

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
https://hiveapi.actifit.io	0.0	1.28.7
https://api.openhive.network	0.03	1.28.7
https://rpc.mahdiyari.info	0.07	1.28.3
https://api.hive.blog	0.1	1.28.7
https://api.syncad.com	0.12	1.28.7
https://techcoderx.com	0.19	1.28.7

Node Uptime Statistics (7-day period)

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

node	uptime %	total checks
https://api.hive.blog	100.0%	168
https://techcoderx.com	99.41%	169
https://api.syncad.com	93.85%	179
https://rpc.mahdiyari.info	89.84%	187
https://anyx.io	50.0%	336
https://api.c0ff33a.uk	50.0%	336
https://api.openhive.network	50.0%	336
https://hive-api.arcange.eu	50.0%	336
https://hive-api.dlux.io	50.0%	336
https://hiveapi.actifit.io	50.0%	336
https://api.deathwing.me	0%	0
https://api.hive.blue	0%	0
https://hive-api.3speak.tv	0%	0
https://hive.roelandp.nl	0%	0
https://hived.emre.sh	0%	0
https://rpc.ausbit.dev	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
https://rpc.mahdiyari.info	257	8.56
https://api.hive.blog	255	8.47
https://techcoderx.com	134	4.46
https://api.syncad.com	104	3.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
https://hiveapi.actifit.io	15407	546.74
https://api.openhive.network	9701	322.83
https://api.syncad.com	8601	274.44
https://api.hive.blog	8000	266.4
https://techcoderx.com	6701	222.11
https://rpc.mahdiyari.info	5701	188.53

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]
https://hiveapi.actifit.io	0.04
https://api.openhive.network	0.07
https://rpc.mahdiyari.info	0.2
https://api.hive.blog	0.22
https://api.syncad.com	0.25
https://techcoderx.com	0.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.

node	blocks behind	head blocks behind irreversible
https://api.openhive.network	0	0
https://hiveapi.actifit.io	0	0
https://rpc.mahdiyari.info	0	0
https://api.hive.blog	0	0
https://api.syncad.com	0	0
https://techcoderx.com	3	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
https://anyx.io	✗ failing	✗ failing	✗ failing	✗ failing	✗ failing
https://api.c0ff33a.uk	✗ failing	✓ stable	✓ stable	✓ stable	↗ improving
https://api.hive.blog	n/a	n/a	↗ improving	↗ improving	↗ improving
https://api.openhive.network	✗ failing	✓ stable	↗ improving	✓ stable	✓ stable
https://api.syncad.com	✓ stable	↗ improving	↗ improving	↗ improving	↗ improving
https://hive-api.arcange.eu	✗ failing	✗ failing	✗ failing	✗ failing	✗ failing
https://hive-api.dlux.io	✗ failing	✗ failing	✗ failing	✗ failing	✗ failing
https://hiveapi.actifit.io	✗ failing	↗ improving	✓ stable	✓ stable	✓ stable
https://rpc.mahdiyari.info	↗ improving	n/a	↗ improving	↗ improving	↗ improving
https://techcoderx.com	✓ stable	↗ improving	↗ improving	↗ improving	✓ stable

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
https://api.openhive.network	0.0	0.55	0.59	0.25	0.59
https://techcoderx.com	0.47	0.86	0.58	0.54	1.09
https://api.c0ff33a.uk	0.0	0.0	0.54	0.31	1.51
https://api.hive.blog	0.69	1.21	0.66	0.53	1.02
https://rpc.mahdiyari.info	0.55	1.07	0.63	0.56	1.31
https://api.syncad.com	0.52	1.6	0.66	0.54	1.05
https://hiveapi.actifit.io	0.0	0.98	0.32	0.0	1.95
https://hive-api.dlux.io	0.0	0.0	0.0	0.0	0.0
https://anyx.io	0.0	0.0	0.0	0.0	0.0
https://hive-api.arcange.eu	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
https://hiveapi.actifit.io	43.75	n/a	1	1	1	2
https://api.openhive.network	41.25	n/a	2	2	2	1
https://rpc.mahdiyari.info	40.8	1	6	3	3	3
https://api.hive.blog	38.4	2	4	4	4	4
https://api.syncad.com	33.6	4	3	5	5	5
https://techcoderx.com	28.8	3	5	6	6	6
https://hive-api.dlux.io	0.0	n/a	n/a	n/a	n/a	n/a
https://api.c0ff33a.uk	0.0	n/a	n/a	n/a	n/a	n/a
https://anyx.io	0.0	n/a	n/a	n/a	n/a	n/a
https://hive-api.arcange.eu	0.0	n/a	n/a	n/a	n/a	n/a