EOL.WikiEOL.Wiki
← ← Back to all products

Fluent BitEnd of Life (EOL) Dates & Support Status

Active
Tools & MonitoringLatest Version: 5.1.2Latest Release: Sep 5, 2026

Fluent Bit is a lightweight log processor and forwarder for collecting and shipping telemetry data.

Support summary

Fluent Bit 5.0 reaches EOL in 40 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Nov 6, 2026

Fluent Bit 5.0 · 40 days left

Supported cycles

2

0 lts

Versions

26

Latest Version

5.1.2

Active Support

2

EOL

24

Lifecycle Timeline

Apr 18, 2023As of Sep 27, 2026
5.1Active · Date not announced
5.0Active · Nov 6, 2026
4.2EOL · Jun 30, 2026
4.1EOL · Feb 11, 2026
4.0EOL · Dec 24, 2025
3.2EOL · Jun 29, 2025
3.1EOL · Feb 12, 2025
3.0EOL · Oct 8, 2024
2.2EOL · Jun 21, 2024
2.1EOL · Feb 6, 2024
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.1Aug 6, 2026MaintainedDate not announced5.1.2No
Active
5.0Mar 31, 2026MaintainedNov 6, 20265.0.10No
Active
4.2Nov 11, 2025EndedJun 30, 20264.2.8No
EOL
4.1Sep 24, 2025EndedFeb 11, 20264.1.2No
EOL
4.0Mar 29, 2025EndedDec 24, 20254.0.14No
EOL
3.2Nov 12, 2024EndedJun 29, 20253.2.10No
EOL
3.1Jul 8, 2024EndedFeb 12, 20253.1.10No
EOL
3.0Mar 21, 2024EndedOct 8, 20243.0.7No
EOL
2.2Nov 6, 2023EndedJun 21, 20242.2.3No
EOL
2.1Apr 18, 2023EndedFeb 6, 20242.1.10No
EOL
2.0Oct 25, 2022EndedJul 19, 20232.0.14No
EOL
1.9Mar 11, 2022EndedDec 5, 20221.9.10No
EOL
1.8Jul 7, 2021EndedDec 5, 20221.8.15No
EOL
1.7Feb 14, 2021EndedEnded; date not announced1.7.9No
EOL
1.6Oct 8, 2020EndedEnded; date not announced1.6.10No
EOL
1.5Jul 13, 2020EndedEnded; date not announced1.5.7No
EOL
1.4Mar 25, 2020EndedEnded; date not announced1.4.6No
EOL
1.3Sep 30, 2019EndedEnded; date not announced1.3.11No
EOL
1.2Jun 26, 2019EndedEnded; date not announced1.2.2No
EOL
1.1May 8, 2019EndedEnded; date not announced1.1.3No
EOL
1.0Dec 13, 2018EndedEnded; date not announced1.0.6No
EOL
0.14Aug 29, 2018EndedEnded; date not announced0.14.9No
EOL
0.13Apr 30, 2018EndedEnded; date not announced0.13.8No
EOL
0.12Aug 17, 2017EndedEnded; date not announced0.12.19No
EOL
0.11Mar 30, 2017EndedEnded; date not announced0.11.17No
EOL
0.10Dec 30, 2016EndedEnded; date not announced0.10.1No
EOL

Data sources

Embed this badge

Fluent Bit end-of-life support status badge

Show Fluent Bit's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Fluent Bit end-of-life status](https://eol.wiki/badge/fluent-bit.svg)](https://eol.wiki/fluent-bit/)

HTML

<a href="https://eol.wiki/fluent-bit/"><img src="https://eol.wiki/badge/fluent-bit.svg" alt="Fluent Bit end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of Fluent Bit have reached end of life?
The following Fluent Bit versions have reached end of life and no longer receive security updates: 4.2, 4.1, 4.0, 3.2, 3.1, 3.0, 2.2, 2.1 (and 16 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Fluent Bit 4.2?
Fluent Bit 4.2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Fluent Bit?
The latest version of Fluent Bit is 5.1.2, released in the 5.1 release cycle.
How many versions of Fluent Bit are currently supported?
Fluent Bit currently has 2 actively supported version(s): 5.1, 5.0.
When does Fluent Bit 5.1 reach end of life?
Fluent Bit 5.1 does not have a specific end-of-life date announced yet.
What should I do when Fluent Bit reaches end of life?
When a Fluent Bit version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.