What happens when a price ticks up mid-day

Routes checked more than once a day (see why the hourly pipeline exists) can genuinely see a fare rise between one check and the next — airlines adjust prices continuously. What happens to that day's recorded price is a small detail with a real answer.

The rule: cheapest seen that day wins

If a route is checked multiple times in one day, we keep the lowest price actually seen, not just the most recent one. A fare that dipped to $400 at 9am and rose to $450 by 3pm gets recorded as a $400 day, because $400 genuinely happened and is the number that matters for anyone deciding whether today was a good day to book.

A real bug this fixed

This wasn't always true. An earlier version of the same-day update logic simply overwrote the stored price with whatever the latest check saw — meaning a price that ticked up later in the day could silently erase a genuinely cheaper fare from the record, understating that day's real cheapest price and subtly skewing the trailing average everything else depends on. We found and fixed this by applying the same "cheapest wins" principle already used when comparing multiple results within a single fetch, extended across a full day's worth of checks.

Where this matters and where it doesn't

This only affects routes checked more than once a day — today, that's the hourly multi-origin pipeline, not JFK's own once-daily job, which was never exposed to the bug in the first place since it only ever gets one number per day regardless.

See today's board