← ← Back to all products
All badges & lifecycle API →
GoAccessEnd of Life (EOL) Dates & Support Status
Active
Tools & MonitoringLatest Version: 1.12Latest Release: Sep 15, 2026
GoAccess is a real-time web log analyzer and interactive viewer for monitoring web server traffic.
Support summary
GoAccess 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
1
Latest Version
1.12
Active Support
1
EOL
0
Lifecycle Timeline
Jun 9, 2016As of Sep 27, 2026
1Active · Date not announced
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
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 1 | Jun 9, 2016 | Maintained | Date not announced | 1.12 | No | Active |
Data sources
Embed this badge
Show GoAccess'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
[](https://eol.wiki/goaccess/)HTML
<a href="https://eol.wiki/goaccess/"><img src="https://eol.wiki/badge/goaccess.svg" alt="GoAccess end-of-life status" height="20"></a>Frequently Asked Questions
Is it safe to continue using GoAccess 1?
GoAccess 1 is currently supported and receiving updates. You can continue using it safely until its end-of-life date.
What is the latest version of GoAccess?
The latest version of GoAccess is 1.12, released in the 1 release cycle.
How many versions of GoAccess are currently supported?
GoAccess currently has 1 actively supported version(s): 1.
When does GoAccess 1 reach end of life?
GoAccess 1 does not have a specific end-of-life date announced yet.
What should I do when GoAccess reaches end of life?
When a GoAccess 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.