## Full API node update - (26/6/2022)
2022-06-25T19:00:10 - 2022-06-26T20:00:20 (UTC)
@fullnodeupdate provides daily updates about the state of all available full API node server for HIVE.
More information about full nodes and a complete RPC node list can be fund in this [post](https://steemit.com/full-nodes/@fullnodeupdate/full-api-node-update---762018).
### 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 30 seconds.

|node | hours with failure | percentage |
| --- | --- | --- |
| https://api.openhive.network | 1/24 | 4.2 % |
| https://hived.privex.io | 3/24 | 12.5 % |
| https://api.hivekings.com | 24/24 | 100.0 % |
| https://fin.hive.3speak.co | 24/24 | 100.0 % |
| https://rpc.ecency.com | 24/24 | 100.0 % |

### List of working nodes (At least once in the last 24h)
This table includes all nodes which were able to a `get_config` call in 30 seconds.The achieved  mean duration values are shown. The returned version is also shown.When a node failes, its mean value is increased as it is counted as 30 seconds

|node |  mean time [s] | version  |
| --- | --- | ---  |
| https://api.deathwing.me | 0.21 | 1.25.0 |
| https://hived.emre.sh | 0.24 | 1.25.0 |
| https://rpc.ausbit.dev | 0.29 | 1.25.0 |
| https://hive-api.arcange.eu | 0.39 | 1.25.0 |
| https://api.hive.blog | 0.40 | 1.25.0 |
| https://api.c0ff33a.uk | 0.57 | 1.25.0 |
| https://api.pharesim.me | 0.76 | 1.25.0 |
| https://anyx.io | 0.76 | 1.25.0 |
| https://api.openhive.network | 1.32 | 1.25.0 |
| https://hive.roelandp.nl | 2.24 | 1.25.0 |
| https://techcoderx.com | 4.61 | 1.25.0 |
| https://hived.privex.io | 38.88 | 1.25.0 |

## Streaming blocks
In this test, it is measured how many blocks a node can stream in 30 seconds.

### List of working nodes - block streaming

This table includes all nodes which were able to stream at least one block within 30 seconds.The achieved minimum, maximum and mean blocks per seconds values are shown. When a node failes, its mean value is reduced as it is counted as 0 blocks per seconds

| node | block/s | mean block/s |
| --- | --- | --- |
| https://hived.emre.sh | 20.7 - 27.9 | 24.1  |
| https://api.deathwing.me | 18.5 - 25.3 | 22.4  |
| https://rpc.ausbit.dev | 11.2 - 15.4 | 13.5  |
| https://api.c0ff33a.uk | 8.3 - 10.0 | 9.3  |
| https://hive-api.arcange.eu | 0.7 - 12.4 | 8.1  |
| https://api.hive.blog | 2.3 - 8.3 | 7.1  |
| https://api.pharesim.me | 6.2 - 7.3 | 7.1  |
| https://anyx.io | 3.3 - 6.0 | 4.5  |
| https://techcoderx.com | 2.2 - 4.0 | 3.7  |
| https://api.openhive.network | 1.1 - 4.8 | 3.0  |
| https://hive.roelandp.nl | 1.3 - 1.7 | 1.5  |
| https://hived.privex.io | 0.0 - 0.0 | 0.0  |

## Measuring irreversible block delays
In this test, the time delay of the irreversible block to the current time is measured.

### List of working nodes - block delays

This table includes all nodes which were able to stream at least one block within 30 seconds.The achieved minimum, maximum and mean irreversible block delay times in seconds are shown. When a node failes, its mean value is reduced as it is counted as 120 seconds.

| node | block delay |  mean delay |
| --- | --- | --- |
| https://api.pharesim.me | 47.00 - 83.70 | 58.880 |
| https://api.hive.blog | 47.86 - 77.87 | 60.440 |
| https://rpc.ausbit.dev | 49.63 - 76.43 | 61.519 |
| https://api.c0ff33a.uk | 47.39 - 77.58 | 62.044 |
| https://api.deathwing.me | 48.67 - 79.49 | 62.348 |
| https://hive-api.arcange.eu | 48.24 - 82.11 | 62.389 |
| https://techcoderx.com | 50.69 - 80.99 | 63.484 |
| https://hived.emre.sh | 49.42 - 84.83 | 66.536 |
| https://api.openhive.network | 46.52 - 70.48 | 71.140 |
| https://hive.roelandp.nl | 52.62 - 78.57 | 78.188 |
| https://anyx.io | 54.73 - 77.22 | 94.660 |

## Account history
In this test, it is measured how many account operation a node can stream.

### List of working nodes - account history
This table includes all nodes which were able to stream at least one account history operation within 15 seconds.The achieved minimum, maximum and mean account transaction per seconds values are shown. When a node failes, its mean value is reduced as it is counted as 0 history operation per seconds

| node | hist/s | mean hist/s |
| --- | --- | --- |
| https://hived.emre.sh | 1251.7 - 1804.3 | 1541.0 |
| https://api.deathwing.me | 810.7 - 1524.7 | 1318.5 |
| https://rpc.ausbit.dev | 801.9 - 1091.9 | 979.2 |
| https://api.c0ff33a.uk | 320.5 - 792.1 | 684.9 |
| https://hive-api.arcange.eu | 56.3 - 992.8 | 637.9 |
| https://api.pharesim.me | 551.2 - 639.9 | 606.1 |
| https://anyx.io | 408.5 - 446.1 | 430.5 |
| https://api.openhive.network | 15.3 - 638.4 | 393.5 |
| https://techcoderx.com | 249.7 - 330.1 | 300.5 |
| https://api.hive.blog | 212.1 - 362.8 | 297.4 |
| https://hive.roelandp.nl | 112.1 - 146.5 | 124.1 |
| https://hived.privex.io | 0.0 - 0.0 | 0.0 |

## Receiving a vote, a comment, and an account 
In this test, the mean duration to receive an account, a comment, and a vote is measured.

### List of working nodes - api calls
This table includes all nodes which were able to answer all three api calls within 30 seconds.The achieved minimum, maximum and mean time durations are shown. When a node failes, its mean value is increased as it is counted as 30 seconds

|node | time [s] | mean time [s] |
| --- | --- | --- |
| https://api.pharesim.me | 0.24 - 0.30 | 0.256 |
| https://hive-api.arcange.eu | 0.13 - 0.83 | 0.277 |
| https://api.hive.blog | 0.23 - 1.18 | 0.332 |
| https://techcoderx.com | 0.45 - 0.62 | 0.495 |
| https://anyx.io | 0.55 - 0.80 | 0.670 |
| https://hive.roelandp.nl | 0.83 - 1.49 | 1.162 |
| https://api.openhive.network | 0.07 - 1.60 | 5.465 |
| https://hived.privex.io | 8.62 - 23.12 | 26.416 |

### Summary of working nodes for HIVE
A node is working, when it could fullfil at least once in the last 24h the following conditions:
* returned data within 30 seconds,
* blocks could be streamed,
* account history was possible,
* votes, a comment, an account could  successfully be fetched and were not empty.

The nodes in the following table are ranked by the mean rank of all three node tables shown above.
This table includes only nodes which were passing all three tests sucessfully.

The shown ranks are: `block rank` - `block_diff rank` - `history rank` - `apicall rank`

| node | ranks | score  |
| --- | --- | --- |
| https://rpc.ausbit.dev | 3 - 4 - 4 - 1 | 83.3 |
| https://api.deathwing.me | 2 - 6 - 7 - 3 | 76.7 |
| https://api.hive.blog | 6 - 3 - 1 - 7 | 71.7 |
| https://api.c0ff33a.uk | 4 - 5 - 6 - 2 | 70.0 |
| https://hived.emre.sh | 1 - 9 - 9 - 4 | 66.7 |
| https://hive-api.arcange.eu | 5 - 7 - 8 - 6 | 58.3 |
| https://api.pharesim.me | 7 - 2 - 12 - 5 | 53.3 |
| https://anyx.io | 8 - 12 - 2 - 9 | 43.3 |
| https://api.openhive.network | 10 - 10 - 3 - 11 | 36.7 |
| https://techcoderx.com | 9 - 8 - 10 - 8 | 31.7 |
| https://hive.roelandp.nl | 11 - 11 - 5 - 10 | 30.0 |
| https://hived.privex.io | 12 - 1 - 11 - 12 | 28.3 |



## Set fully working nodes with beempy / steempy
https://api.steemitstage.com, https://api.steemitdev.com and nodes with not working results were excluded.
### `beempy`
```
beempy set nodes "['https://rpc.ausbit.dev', 'https://api.deathwing.me', 'https://api.hive.blog', 'https://api.c0ff33a.uk', 'https://hived.emre.sh', 'https://hive-api.arcange.eu', 'https://api.pharesim.me', 'https://anyx.io', 'https://api.openhive.network', 'https://techcoderx.com', 'https://hive.roelandp.nl', 'https://hived.privex.io']"
```
### `steempy`
```
steempy set nodes https://rpc.ausbit.dev,https://api.deathwing.me,https://api.hive.blog,https://api.c0ff33a.uk,https://hived.emre.sh,https://hive-api.arcange.eu,https://api.pharesim.me,https://anyx.io,https://api.openhive.network,https://techcoderx.com,https://hive.roelandp.nl,https://hived.privex.io
```



## Receive fully working nodes from `json_metadata` of the @fullnodeupdate account 
The nodes are  also stored in the `json_metadata` variable of the @fullnodeupdate account.
The nodes inside the account metadata are updated every hour.
The json_metadata includes the following data:

* `nodes` - list of nodes that passed all tests.
* `failing_nodes` - list of nodes that did not answer the `get_config` call.
* `report` - test results.
* `parameter` - used `beem` and test parameter.

Example code for python: 
```
from beem.account import Account
import json
acc = Account("fullnodeupdate")
nodes = json.loads(acc["json_metadata"])["nodes"]
acc.steem.set_default_nodes(nodes)
```


___
If you like what I'm doing, please consider @holger80 as one of your witnesses. You can use [hivesigner.com for approve your vote](https://hivesigner.com/sign/account-witness-vote?witness=holger80&approve=1) or go to https://peakd.com/witnesses and vote for me
___
This post was created with [beem](https://github.com/holgern/beem), my python library for steem.