← ← Back to all products
Matomo
Active
CMS & ContentLatest Version: 5.11.2Latest Release: Jun 17, 2026
Matomo is an open-source web analytics platform and privacy-friendly alternative to Google Analytics.
Support summary
Matomo 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
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
5
Latest Version
5.11.2
Active Support
1
EOL
4
Lifecycle Timeline
Today ↓
5
5
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5 | Dec 18, 2023 | Yes | No | 5.11.2 | No | Active |
| 4 | Nov 24, 2020 | Dec 18, 2023 | Dec 19, 2024 | 4.16.2 | No | EOL |
| 3 | Dec 19, 2016 | Nov 24, 2020 | Dec 1, 2021 | 3.14.1 | No | EOL |
| 2 | Dec 17, 2013 | Dec 19, 2016 | Dec 18, 2017 | 2.18.1 | No | EOL |
| 1 | Aug 28, 2010 | Dec 17, 2013 | Dec 17, 2013 | 1.12 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Matomo have reached end of life?
The following Matomo versions have reached end of life and no longer receive security updates: 4, 3, 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Matomo 4?
Matomo 4 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 Matomo?
The latest version of Matomo is 5.11.2, released in the 5 release cycle.
How many versions of Matomo are currently supported?
Matomo currently has 1 actively supported version(s): 5.
When does Matomo 5 reach end of life?
Matomo 5 does not have a specific end-of-life date announced yet.
What should I do when Matomo reaches end of life?
When a Matomo 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.