ShutdownRadar
Support lifecycle

arangodb end of life dates — full support timeline

12 of 14 tracked arangodb releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
3.122024-03-21not announced3.12.9.4supported
3.112023-05-23not announced3.11.14.4supported
3.102022-09-292024-04-153.10.14ended
3.92022-02-072023-09-153.9.12ended
3.82021-07-142023-04-303.8.9ended
3.72020-04-102022-05-313.7.18ended
3.62019-12-302021-08-313.6.16ended
3.52019-08-142020-12-313.5.7ended
3.42018-12-052020-06-213.4.11ended
3.32017-12-142020-02-293.3.25ended
3.22017-07-192019-03-313.2.18ended
3.12016-11-02ended3.1.29ended
3.02016-06-22ended3.0.12ended
2.82016-01-252018-06-152.8.11ended

Who is affected

Anyone running an unsupported arangodb release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/arangodb, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next arangodb deadline

You are reading this because a arangodb release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every arangodb and related deadline as it is announced, with exact dates and primary sources.

Watch arangodb deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive