ShutdownRadar
Support lifecycle

consul end of life dates — full support timeline

15 of 18 tracked consul releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
2.02026-05-24not announced2.0.2supported
1.222025-10-27not announced1.22.7supported
1.212025-05-06not announced1.21.5supported
1.202024-10-142026-05-241.20.6ended
1.192024-06-122025-10-271.19.2ended
1.182024-02-262025-05-061.18.2ended
1.172023-11-032024-10-141.17.4ended
1.162023-06-262024-06-121.16.7ended
1.152023-02-232024-02-271.15.11ended
1.142022-11-152023-11-031.14.11ended
1.132022-08-092023-06-261.13.9ended
1.122022-04-192023-02-231.12.9ended
1.112021-12-142022-11-151.11.11ended
1.102021-06-222022-08-091.10.12ended
1.92020-11-242022-04-191.9.17ended
1.82020-06-182021-12-141.8.19ended
1.72020-02-112021-06-221.7.14ended
1.62019-08-232020-11-241.6.10ended

Who is affected

Anyone running an unsupported consul release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/consul, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next consul deadline

You are reading this because a consul release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every consul and related deadline as it is announced, with exact dates and primary sources.

Watch consul deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive