Two captive core both in synced state but report different ledger number

Question

Have anyone experienced this. I deploy two instances of Horizon service each with its own captive-core. After a while, both captive-core caught up and when I query its :11626/info endpoint both report State: Synced!. However, after a while their info.ledger.num return a different number (one instance always lag behind).