Since its inception Hive has gained and lost public API nodes. Recent growth of Hive increased the demand on the current infrastructure and rotation of public nodes, making the move to scale capacity a no-brainer.

The new node is hived with account history + hivemind via jussi and can be used by pointing your app to https://api.hive.blue. It joins our network of witness primary/backup nodes (which are normally kept at one primary and two backups for the duration of the year and increased during forks), our seed node seed.hive.blue:2001, and other supporting infrastructure.

Is there a problem?

A problem doesn't need to develop for there to be a proactive solution. Hive is doing great right now and always has been. We've been on a solid trajectory upwards in terms of utility and growth as a decentralized Web3 ecosystem of both the present and the future. There is a growing number of contributors to the technical side and as always, more and more people are choosing to build their unique visions on Hive. To help them achieve this, we need to always seek to improve our infrastructure and make it as reliable and resilient as possible.

Proactive scaling means increasing various infrastructure elements, updating and strengthening the required processes and servers, as well as diversifying our individual capabilities. What this means is if an important application runs on an overburdened/oversubscribed VPS, moving it to a larger instance or even a dedicated instance. Potatoes are alright for things that don't see constant use, but we believe they're not acceptable for key infrastructure.

About api.hive.blue

We are looking forward to see what kind of throughput we can push via this node, offloading and relieving some of the pressure on existing nodes. We monitor our infrastructure actively both to share interesting metrics with the rest of the Hive API node operators, as well as to identify any performance or security concerns that may arise. We have seen directed attempts to degrade API performance, or overwhelm services by DDoS on existing API nodes; such activities will be closely monitored and deterred.

Technical Specs

• API
  • Located in sunny Finland DC
  • 1Gbps IPv4 and IPv6 connectivity
  • i9-9900K CPU
  • 128GB RAM
  • 2x 1TB NVMe
  • 2x 1TB SSD
• Seed / Related services
  • Germany DC
  • 1Gbps IPv4 and IPv6 connectivity
  • Ryzen 9 3900 CPU
  • 128GB RAM
  • 2x 512GB NVMe

Like what we're doing? Support us by voting for the Hive account@guiltyparties witness.