You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a chaingraph instance which tracks two networks: BCH chipnet and mainnet. Recently the p2p enpoint I have chosen some 1.5 years ago randomly turned out to belong to uname who took it down (temporarily?) because of excessive traffic, it became unresponsibele and many errors were to seen in console. All okay but mainnet sync got stalling because of this and my iinstance got out of sync for 2 days until noticed by consumers. As soon as I have switched my chipnet endpoint to communicate with other well-available peer, both chipnet nodes and mainnet nodes started to catch up. Please take a look
The text was updated successfully, but these errors were encountered:
I have a chaingraph instance which tracks two networks: BCH chipnet and mainnet. Recently the p2p enpoint I have chosen some 1.5 years ago randomly turned out to belong to uname who took it down (temporarily?) because of excessive traffic, it became unresponsibele and many errors were to seen in console. All okay but mainnet sync got stalling because of this and my iinstance got out of sync for 2 days until noticed by consumers. As soon as I have switched my chipnet endpoint to communicate with other well-available peer, both chipnet nodes and mainnet nodes started to catch up. Please take a look
The text was updated successfully, but these errors were encountered: