Intel Processors End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Intel Processors versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Ivy Bridge (Xeon E5v2/E7v2) | — | Apr 29, 2012 | Jun 30, 2020 | 2231 days past EOL | EOL |
| Ivy Bridge | — | Apr 29, 2012 | Dec 31, 2019 | 2413 days past EOL | EOL |
| Centerton | — | Dec 11, 2012 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Cherry Trail | — | Mar 2, 2013 | Jun 30, 2022 | 1501 days past EOL | EOL |
| Briarwood | — | Apr 1, 2013 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Crystal Well | — | Jun 2, 2013 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Haswell (Xeon E5v3/E7v3) | — | Jun 4, 2013 | Dec 31, 2021 | 1682 days past EOL | EOL |
| Haswell | — | Jun 4, 2013 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Avoton | — | Jul 1, 2013 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Bay Trail | — | Sep 11, 2013 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Devil's Canyon | — | Jun 2, 2014 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Broadwell DE | — | Oct 27, 2014 | Dec 31, 2022 | 1317 days past EOL | EOL |
| Broadwell (Xeon E7v4/E7v4) | — | Oct 27, 2014 | Jun 30, 2022 | 1501 days past EOL | EOL |
| Broadwell | — | Oct 27, 2014 | Jun 30, 2021 | 1866 days past EOL | EOL |
| Braswell | — | Mar 1, 2015 | Jun 30, 2022 | 1501 days past EOL | EOL |
| Skylake | — | Aug 5, 2015 | Sep 30, 2022 | 1409 days past EOL | EOL |
| Kaby Lake | — | Aug 30, 2015 | Mar 31, 2024 | 861 days past EOL | EOL |
| Apollo Lake | — | Aug 30, 2016 | Jun 30, 2023 | 1136 days past EOL | EOL |
| Coffee Lake | — | Oct 5, 2017 | Jun 30, 2025 | 405 days past EOL | EOL |
| Gemini Lake | — | Dec 11, 2017 | Dec 31, 2024 | 586 days past EOL | EOL |
| Cannon Lake | — | May 1, 2018 | Sep 30, 2021 | 1774 days past EOL | EOL |
| Comet Lake | — | Aug 21, 2019 | TBD | Supported | Active |
| Ice Lake | — | Sep 1, 2019 | TBD | Supported | Active |
| Lakefield | — | Jun 19, 2020 | Jun 30, 2023 | 1136 days past EOL | EOL |
| Tiger Lake | — | Sep 2, 2020 | TBD | Supported | Active |
| Elkhart Lake | — | Sep 23, 2020 | TBD | Supported | Active |
| Jasper Lake | — | Jan 11, 2021 | TBD | Supported | Active |
| Rocket Lake | — | Mar 30, 2021 | TBD | Supported | Active |
| Alder Lake | — | Nov 4, 2021 | TBD | Supported | Active |
| Raptor Lake | — | Oct 20, 2022 | TBD | Supported | Active |
| Meteor Lake | — | Dec 14, 2023 | TBD | Supported | Active |
| Lunar Lake | — | Sep 24, 2024 | TBD | Supported | Active |
| Arrow Lake | — | Oct 24, 2024 | TBD | Supported | Active |
| Panther Lake | — | Jan 6, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/intel-processors)
What does Intel Processors end of life mean for your organization?
When a version of Intel Processors reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Intel Processors should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Intel Processors reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Intel Processors from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →