Jun 13, 2025

There are a large number of peers, entirely in the version 27.1 - 27.2 range, that have a significant clock skew in their version message. There are a very small number over the entire network that exceed even +/- 1 minute, but these versions commonly reach as high as 5,100 minutes behind (never ahead). We've started dropping peers for excessive skew, which I've made configurable. Anyone aware of such an issue with Core nodes?