← ← Back to all products
CentOS Stream
Active
Operating SystemsLatest Version: 10Latest Release: N/A
CentOS Stream is a continuously delivered Linux distribution that tracks ahead of RHEL, serving as the upstream for future RHEL releases.
Support summary
CentOS Stream currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
May 31, 2027
CentOS Stream 9 · 341 days left
Supported cycles
2
0 lts
Versions
3
Latest Version
10
Active Support
2
EOL
1
Lifecycle Timeline
Today ↓
10
10
9
9
8
8
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 10 | Dec 12, 2024 | Jan 1, 2030 | Jan 1, 2030 | 10 | No | Active |
| 9 | Sep 15, 2021 | May 31, 2027 | May 31, 2027 | 9 | No | Active |
| 8 | Sep 24, 2019 | May 31, 2024 | May 31, 2024 | 8 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of CentOS Stream have reached end of life?
The following CentOS Stream versions have reached end of life and no longer receive security updates: 8. It is recommended to upgrade to a supported version.
Is it safe to continue using CentOS Stream 8?
CentOS Stream 8 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 CentOS Stream?
The latest version of CentOS Stream is 10, released in the 10 release cycle.
How many versions of CentOS Stream are currently supported?
CentOS Stream currently has 2 actively supported version(s): 10, 9.
When does CentOS Stream 10 reach end of life?
CentOS Stream 10 is scheduled to reach end of life on Jan 1, 2030.
What should I do when CentOS Stream reaches end of life?
When a CentOS Stream 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.