Leap seconds exist because the Earth takes (very roughly) about a millisecond more than 24 * 60 * 60 seconds to rotate each day; when we have accumulated enough extra milliseconds, a leap second is inserted into UTC to keep it in sync with the Earth. At the moment the Earth is rotating faster than in recent decades: these shorter days, with a lower length-of-day, means the milliseconds accumulate more slowly, and we get fewer leap seconds. [...]
Michael Deckers said in his LEAPSECS message that we haven't seen a rate difference as low as zero since 1961! This implies that unless something wild happens, we are very unlikely to have a leap second in the next few years. [...]
The absence of leap seconds has the advantage that leap second bugs don't get tickled, but it has the disadvantage that timekeeping code might rot and new bugs or regressions can be introduced without anyone noticing. Even worse is the risk of the length of day getting shorter which could in theory mean we might need a negative leap second. There has never been a negative leap second, and if there is one, everyone who deals with NTP or kernel timekeeping code expects that it will be an appalling shitshow.
Clearly the best, most proactive solution here is to arrange for something very, very large to hit the Earth while traveling West.