check / check (push) Canceled after 0s
A batch's prefix times were taken from each peer's last update for the prefix, and the latest of those was kept. The prefix tables hold only first_seen, written when the prefix is new, so a prefix announced by two peers seconds apart in one batch was stored first seen at the later time, and the IP lookup could answer with a first_seen after the route's last_seen. The flush now keeps, for each prefix, the earliest timestamp among all of the batch's updates for it. Model: opus-5-5