DDoS Attacks on Hive Engine Node Network: What’s Going On and How to Stay Connected

Over the past 24 hours, hive-engine node network has been under heavy stress due to a series of #DDoS attacks. As of this afternoon, many nodes are still struggling to recover and maintain stability. This has caused noticeable delays and connection issues for users interacting with hive-engine and Tribaldex websites.

For those who rely on these services daily, the disruptions have been frustrating — but there’s a practical workaround: first of all, you can host your own hive-engine node. Other are doing this and connect their nodes even to the internet and make them publicly available for us.

Getting Node URLs

If you’re not running your own node yet, don’t worry — the Hive community has made things easier. The user Hive account@thecrazygm has created a system that provides many hive-engine node URLs. You can find these URLs in the account’s metadata on Hive (Hive account@flowerengine).

You have two options:

1. Run the Node.js service locally provided by Hive account@thecrazygm.

https://github.com/TheCrazyGM/flowerengine-js

1. Manually retrieve node URLs from the HiveDev site

https://hivehub.dev/@flowerengine

Both hive-engine and Tribaldex support features that allow you to connect directly to a local RPC. This ensures you’re not dependent on overloaded public nodes and can continue operating smoothly even during network instability.

Here’s how you can set it up:

For hive-engine:

1. Open the hive-engine website.
2. Click the gear icon at the bottom right corner of the site.
3. In the dialog box that appears, paste your node’s URL.
4. Close the dialog and reload the website — your connection will now route through your chosen node.

For Tribaldex:
The process is identical. Open the Tribaldex site, click the same gear symbol, and enter your node URL in the settings dialog.