The page have received an update to mitigate the issues when one or more of the backend nodes forking. This is normal, but at times it happens more frequent.
I've looked and worked on the issue for some time and finally found a good way to solve it.
The page runs severel nodes to make sure we always have the correct information. This has so far been working so-so. From now on the page should always follow the node with the longest chain.
