Android End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Android versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Android 17 is supported, with no end-of-life or end-of-support date announced yet. 30 of 34 tracked Android versions are past end of life; the most recent to reach it, 13, did so on March 2, 2026. The full Android lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | — | Sep 23, 2008 | Not published | Past EOL | EOL |
| 1.1 | — | Feb 9, 2009 | Not published | Past EOL | EOL |
| 1.5 | — | Apr 27, 2009 | Not published | Past EOL | EOL |
| 1.6 | — | Sep 15, 2009 | Not published | Past EOL | EOL |
| 2.0 | — | Oct 26, 2009 | Not published | Past EOL | EOL |
| 2.1 | — | Jan 11, 2010 | Not published | Past EOL | EOL |
| 2.2 | — | May 20, 2010 | Not published | Past EOL | EOL |
| 2.3 | — | Dec 6, 2010 | Not published | Past EOL | EOL |
| 3.0 | — | Feb 22, 2011 | Not published | Past EOL | EOL |
| 3.1 | — | May 10, 2011 | Not published | Past EOL | EOL |
| 3.2 | — | Jul 15, 2011 | Not published | Past EOL | EOL |
| 4.0 | — | Oct 18, 2011 | Not published | Past EOL | EOL |
| 4.1 | — | Jul 9, 2012 | Not published | Past EOL | EOL |
| 4.2 | — | Nov 13, 2012 | Not published | Past EOL | EOL |
| 4.3 | — | Jul 24, 2013 | Not published | Past EOL | EOL |
| 4.4 | — | Oct 31, 2013 | Oct 1, 2017 | 3279 days past EOL | EOL |
| 4.4W | — | Mar 31, 2014 | Oct 1, 2017 | 3279 days past EOL | EOL |
| 5.0 | — | Nov 12, 2014 | Mar 1, 2018 | 3128 days past EOL | EOL |
| 5.1 | — | Mar 1, 2015 | Mar 1, 2018 | 3128 days past EOL | EOL |
| 6.0 | — | Oct 5, 2015 | Aug 1, 2018 | 2975 days past EOL | EOL |
| 7.0 | — | Aug 22, 2016 | Oct 1, 2019 | 2549 days past EOL | EOL |
| 7.1 | — | Dec 1, 2016 | Oct 1, 2019 | 2549 days past EOL | EOL |
| 8.0 | — | Aug 21, 2017 | Jan 1, 2021 | 2091 days past EOL | EOL |
| 8.1 | — | Dec 5, 2017 | Jan 10, 2021 | 2082 days past EOL | EOL |
| 9 | — | Aug 6, 2018 | Jan 1, 2022 | 1726 days past EOL | EOL |
| 10 | — | Sep 3, 2019 | Mar 6, 2023 | 1297 days past EOL | EOL |
| 11 | — | Sep 8, 2020 | Feb 5, 2024 | 961 days past EOL | EOL |
| 12 | — | Oct 4, 2021 | Mar 3, 2025 | 569 days past EOL | EOL |
| 12.1 'Snow Cone v2' (aka 12L) | — | Mar 7, 2022 | Mar 3, 2025 | 569 days past EOL | EOL |
| 13 | — | Aug 15, 2022 | Mar 2, 2026 | 205 days past EOL | EOL |
| 14 | — | Oct 4, 2023 | TBD | Supported | Active |
| 15 | — | Sep 3, 2024 | TBD | Supported | Active |
| 16 | — | Jun 10, 2025 | TBD | Supported | Active |
| 17 | — | Jun 16, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/android)
Android release and support pattern
Across the 34 release lines with a published release date, Android has shipped a new line roughly every 5 months (median interval). A line typically stays supported for about 3.4 years from its release to its end-of-life date (measured on the 15 lines with both dates published).
Of the 34 release lines tracked, 30 are past end of life and 4 are still within support; 15 are marked end of life without a published date. The newest line, 17, was released June 16, 2026. No end-of-life date is currently published for the 4 supported lines.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Android security intelligence
CISA KEV history: Android is named in CISA's Known Exploited Vulnerabilities catalog 18 times, most recently on 2026-06-02. Derived from CISA's live catalog at every build.
What does Android end of life mean for your organization?
When a version of Android 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Android 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 Android 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 Android 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 →