Hive is currently going through a Hard Fork and it takes a little time for all the nodes to update from the older fork to the newer one. Such bugs are natural and will get fixed over a bit of time. For now, I suggest using PeakD's Node Benchmark Tool to check which node is the best for you to use in the moment of checking (the ''best'' node might change from time to time, so this is a great tool to check and set your nodes at any time).
You are viewing a single comment's thread from:
I really hoped it would be fixed soon, in fact it happened to me only in Hive, others have had problems accessing peakd, and other people just work well both alternatives. But, since the problem is mostly in the Hive platform, it is good to have this as an alternative,
since in part it is a little more modern and thus get used to it, like hive, while the Error is solved. In my case, I was not to use Peakd much, I did not even publish on it, I only used it to invest on the platform, but now it would not be wrong to take advantage of learning a little more and above all continue sharing.🤗
Thank you very much for the information, I hope it is solved, a greeting and a hug friend @xves. 🥰
🐝