Telegraf End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Telegraf versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.1 | Sep 2, 2016 | Jan 23, 2017 | 3485 days past EOL | EOL |
| 1.1 | 1.1.2 | Nov 8, 2016 | May 15, 2017 | 3373 days past EOL | EOL |
| 1.2 | 1.2.1 | Jan 23, 2017 | Sep 5, 2017 | 3260 days past EOL | EOL |
| 1.3 | 1.3.5 | May 15, 2017 | Dec 14, 2017 | 3160 days past EOL | EOL |
| 1.4 | 1.4.5 | Sep 5, 2017 | Apr 16, 2018 | 3037 days past EOL | EOL |
| 1.5 | 1.5.3 | Dec 14, 2017 | Jun 12, 2018 | 2980 days past EOL | EOL |
| 1.6 | 1.6.4 | Apr 16, 2018 | Sep 21, 2018 | 2879 days past EOL | EOL |
| 1.7 | 1.7.4 | Jun 12, 2018 | Nov 20, 2018 | 2819 days past EOL | EOL |
| 1.8 | 1.8.3 | Sep 21, 2018 | Mar 5, 2019 | 2714 days past EOL | EOL |
| 1.9 | 1.9.5 | Nov 20, 2018 | Jun 11, 2019 | 2616 days past EOL | EOL |
| 1.10 | 1.10.4 | Mar 5, 2019 | Sep 3, 2019 | 2532 days past EOL | EOL |
| 1.11 | 1.11.5 | Jun 11, 2019 | Dec 12, 2019 | 2432 days past EOL | EOL |
| 1.12 | 1.12.6 | Sep 3, 2019 | Mar 26, 2020 | 2327 days past EOL | EOL |
| 1.13 | 1.13.4 | Dec 12, 2019 | Jul 22, 2020 | 2209 days past EOL | EOL |
| 1.14 | 1.14.5 | Mar 26, 2020 | Oct 21, 2020 | 2118 days past EOL | EOL |
| 1.15 | 1.15.4 | Jul 22, 2020 | Dec 18, 2020 | 2060 days past EOL | EOL |
| 1.16 | 1.16.3 | Oct 21, 2020 | Mar 17, 2021 | 1971 days past EOL | EOL |
| 1.17 | 1.17.3 | Dec 18, 2020 | Jun 17, 2021 | 1879 days past EOL | EOL |
| 1.18 | 1.18.3 | Mar 17, 2021 | Sep 17, 2021 | 1787 days past EOL | EOL |
| 1.19 | 1.19.3 | Jun 17, 2021 | Dec 15, 2021 | 1698 days past EOL | EOL |
| 1.20 | 1.20.4 | Sep 17, 2021 | Mar 23, 2022 | 1600 days past EOL | EOL |
| 1.21 | 1.21.4 | Dec 15, 2021 | Jun 13, 2022 | 1518 days past EOL | EOL |
| 1.22 | 1.22.4 | Mar 23, 2022 | Sep 12, 2022 | 1427 days past EOL | EOL |
| 1.23 | 1.23.4 | Jun 13, 2022 | Dec 12, 2022 | 1336 days past EOL | EOL |
| 1.24 | 1.24.4 | Sep 12, 2022 | Mar 13, 2023 | 1245 days past EOL | EOL |
| 1.25 | 1.25.3 | Dec 12, 2022 | Jun 12, 2023 | 1154 days past EOL | EOL |
| 1.26 | 1.26.3 | Mar 13, 2023 | Sep 11, 2023 | 1063 days past EOL | EOL |
| 1.27 | 1.27.4 | Jun 12, 2023 | Dec 11, 2023 | 972 days past EOL | EOL |
| 1.28 | 1.28.5 | Sep 11, 2023 | Mar 11, 2024 | 881 days past EOL | EOL |
| 1.29 | 1.29.5 | Dec 11, 2023 | Jun 10, 2024 | 790 days past EOL | EOL |
| 1.30 | 1.30.3 | Mar 11, 2024 | Sep 9, 2024 | 699 days past EOL | EOL |
| 1.31 | 1.31.3 | Jun 10, 2024 | Dec 9, 2024 | 608 days past EOL | EOL |
| 1.32 | 1.32.3 | Sep 9, 2024 | Mar 10, 2025 | 517 days past EOL | EOL |
| 1.33 | 1.33.3 | Dec 9, 2024 | Jun 16, 2025 | 419 days past EOL | EOL |
| 1.34 | 1.34.4 | Mar 10, 2025 | Sep 8, 2025 | 335 days past EOL | EOL |
| 1.35 | 1.35.4 | Jun 16, 2025 | Dec 8, 2025 | 244 days past EOL | EOL |
| 1.36 | 1.36.4 | Sep 8, 2025 | Mar 9, 2026 | 153 days past EOL | EOL |
| 1.37 | 1.37.3 | Dec 8, 2025 | Jun 8, 2026 | 62 days past EOL | EOL |
| 1.38 | 1.38.4 | Mar 9, 2026 | TBD | Supported | Active |
| 1.39 | 1.39.2 | Jun 8, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/telegraf)
What does Telegraf end of life mean for your organization?
When a version of Telegraf 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 Telegraf 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 Telegraf 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 |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Telegraf versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Telegraf has 38 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Telegraf exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.