This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Network fragmentation on Ropsten? #9549
Labels
F2-bug 🐞
The client fails to follow expected behavior.
M4-core ⛓
Core client code / Rust.
P5-sometimesoon 🌲
Issue is worth doing soon.
Milestone
I can't sync ropsten with either
beta
orstable
, looks like a peering issue, I can only find 3-4 Parity peers and sync is stuck at block599_264
, list of unique peers after two days running from two different clients on Ropsten:Parity-Ethereum/v2.0.5-stable-f7c9c27-20180911/x86_64-linux-gnu/rustc1.28.0
Parity-Ethereum/v2.1.0-beta-f59ba3d-20180911/x86_64-linux-gnu/rustc1.28.0
Parity/v1.10.6-stable-bc0d134-20180605/x86_64-linux-gnu/rustc1.26.2
Parity/v1.11.5-beta-0487c5b-20180629/x86_64-linux-gnu/rustc1.27.0
Parity/v1.11.7-stable-085035f-20180717/x86_64-linux-gnu/rustc1.27.1
Parity/v1.9.2-beta-0feb0bb-20180201/x86_64-linux-gnu/rustc1.23.0
See also https://ropsten-stats.parity.io/
The text was updated successfully, but these errors were encountered: