Today, Tuesday July 17th around 13:17 Hrs (GMT-6), EOS Metal reported that several BPs including 4 of the top 21 were offline, or re-synchronizing the chain. See attached image of in this article.
Apparently this anomalous situation had the query servers or API without responding to external connections, however, several claimed that their production servers are still running.
It was quickly determined that the connectivity problems were caused by failures of the Google Cloud service, mainly in Google’s global balancer (https://status.cloud.google.com/incident/cloud-networking/18012).
Several of the affected BPs reported that internally the public API servers were still downloading blocks and connected to the EOS network, but for the rest of the world they were offline.
This shows us that even though 5% of the BPs did not have external connectivity, the EOS network continued to work and process blocks normally.
It is eosMeso’s pleasure and honor to spread the word on EOS to the LATAM public, business community, regulators, legal profesionals, universities, and everyone in between.
Have you considered voting for eosMeso who is ready for that jump?
Please follow our activities and proposals, reach out with your questions, and please consider a vote for us. Visit us at: https://eosmeso.io or contact us in any of our social network channels: