A while back we added capability to hive-js (one of the primary libraries used to develop frontends like hive.blog) for it to detect when a node starts failing and allow for it to failover to other nodes. The frontends nowadays also allow for you to set which set of nodes you want it to be able to failover too, and the order in which that should take place. Still, there's probably more than can be done to improve the failover process.
You are viewing a single comment's thread from:
Thanks for letting me know. I have seen a few things fail from time to time. When I was on Leofinance, sometimes it doesn't update correctly (I see it update correctly in PeakD and Eccency). Even when changing the node I was viewing on Leofiance, it would not change so it might not be a node problem but a Leofiance problem.
Although besides that error, there are some problems occasionally about fetching delegations and HIVE Engine issues. Sometimes they last longer and others times, they are only around for like 5 minutes.
Posted Using LeoFinance Beta
Not sure why it's not switching on Leofinance, but one possibility is that they don't have it configured to auto-failover to other nodes (each frontend can configure which API nodes it wants to "trust").
Hive engine issues are outside of the scope of what hivemind does, as it is a distinct 2nd layer service with separate infrastructure established for that. I believe they're currently working on decentralizing that infrastructure and making it more robust against single point failures.