Steem.supply Outage - Planning My Own Content Node

Words
305
Reading
2 min
Listen
Play
9y

For about an hour, steem.supply was intermittently down today, due to an outage of one of the public API nodes I'm querying to pull the data. At the moment of writing, seems like the situation is back to normal, albeit the speed is relatively slow.

Starting next month I will deploy my own API node, specifically for this project. It's not a simple, nor cheap job to do, so I'm relaying a lot on community support for this.

At the moment, I'm powering down to put together my own infrastructure for all my Steemit projects*, consisting in:

  • dedicated witness node (currently running on a rented machine on Hetzner)
  • backup witness node (non existing currently)
  • dedicate API node for steem.supply (currently relying on public nodes maintained by Steemit INC or other contributors)
  • development machine (currently my laptop)

All of the above will sit on a bare metal mini cluster I already contracted. On an optimistic timeline, I think I should be up and ready at the end of the first half of October).

Thank you for your understanding and continuous support!

*note: development on steem.city is on hold until infrastructure is up and ready


I'm a serial entrepreneur, blogger and ultrarunner. You can find me mainly on my blog at Dragos Roua where I write about productivity, business, relationships and running. Here on Steemit you may stay updated by following me dragosroua@dragosroua.


Dragos Roua


You can also vote for me as witness here:
https://steemit.com/~witnesses


If you're new to Steemit, you may find these articles relevant (that's also part of my witness activity to support new members of the platform):

Steem.supply Outage - Planning My Own Content Node | Ecency