Archive post
NetworkStatus update : Quality, Hive-Engine History, more tests ....
• bambukah
Hello World! This post is made to bring you a good news : NetworkStatus received an update, and a good one. For those who don't know, this project is a small API for developers to check Hive network to
Hello World! This post is made to bring you a good news : [**NetworkStatus**](https://netstat.hivelive.me) received an update, and a good one.

For those who don't know, this project is a small API for developers to check Hive network to get the best node. If all Hive projects use that, no more "Hive-Engine node error" or "Error from Hive node" will happening.
How ? Do a small query on [**NetworkStatus**](https://netstat.hivelive.me), and the best online node is returned! Do that just before send Hive-Engine query and you'll never have node errors.
So, what's new in this update ?
## Code refactor and code quality
I do a big work to made the code more clean and efficient. The goal is to bring a very easy and fast API to every developer.
For future developments (maybe Open-Source?), every "network" have his file: Hive / Hive-Engine / ... And I do that to make easier maintenance and development for each. Also, every "network" update have his thread so one I cannot have conflicts between them, bringing more stability and viability.
## Hive-Engine History
If you don't know, Hive Engine have two types of node: Standard and History nodes. [**NetworkStatus**](https://netstat.hivelive.me) began with Hive-Engine, but now, you can also have Hive-Engine History nodes check!
At this time, there are only three listed History nodes but [**NetworkStatus**](https://netstat.hivelive.me) already have a system to add one in the fastest way: I just add one line in a file and that's all.

## HiveSQL
A good thing is to check [HiveSQL](https://hivesql.io/) status before sending the query to avoid bad data sending or bugs. [**NetworkStatus**](https://netstat.hivelive.me) have now an (cached) endpoint to check that: `/hivesql`.
This endpoint is refreshed every 5 minutes. Before trying to connect to HiveSQL, just check its state with [**NetworkStatus**](https://netstat.hivelive.me), many bugs can be avoided if HiveSQL is down.
## Hive-Engine
Hive-Engine endpoints also have new features! Lots of data have been added. To start, I've added 3 new tests :
- blockchain.getLastBlock
- blockchain.getBlockInfo
- blockchain.getTransactionInfo
So now, you can know what works on each Hive-Engine node for blockchain endpoint.
Last but not the least, I add a timer! [**NetworkStatus**](https://netstat.hivelive.me) now sort every node by process time (before that, it was by ping... it was not serious). When you use the `/he/best` endpoint, it will show you all the data from the best node only.
## Conclusion
[**NetworkStatus**](https://netstat.hivelive.me) is now a real project to have more stability on Hive-Engine blockchain. But I have many more tests and features to add to this project (Hive node check, other tests functions, ...).
In a near future, I'll implement this in all the [HiveLive](https://hivelive.me) projects to have a real stability on Hive-Engine. That will show you how important [**NetworkStatus**](https://netstat.hivelive.me) is.
If you like my work, don't forget to upvote and/or reblog this post. Please consider making a [donation](https://stream.hivelive.me/donate/bambukah) if you can.
As usual, if you have some questions, feedback or feature request, fell free to comment. See my others Hive project on [HiveLive](https://hivemive.me/). You can join the [HiveLive Discord](https://discord.gg/uJKMb6pGEv) server to talk with us too.
Have a great day!
---
GFX Credits :
- Hive circuit logo by @doze (Thank you so much for your work!)