MongoDB 3.2 lifecycle

Current status

end of lifehigh

MongoDB 3.2 reached end of life on 30 Sept 2018. Security and bug fixes are no longer provided by the project according to published lifecycle data.

Official lifecycle source: MongoDB Server lifecycle schedule

Support phase
end of life
End of life
30 Sept 2018
Latest release
Released

At a glance

Version line
3.2
Initial release
1 Dec 2015
Lifecycle phase
end of life
Latest stable
Latest release date
EOL
30 Sept 2018
Risk
high
Releases tracked
0

Lifecycle timeline

Phases from published LifecyclePeriod records. Missing phases are not inferred.

  1. Release

    1 Dec 2015

  2. standard support

    1 Dec 2015 → 30 Sept 2018

    Source: MongoDB Server lifecycle schedule

  3. end of lifecurrent

    30 Sept 2018 → —

    Source: MongoDB Server lifecycle schedule

MongoDB 3.2 reached end of life on 30 Sept 2018. Security and bug fixes are no longer provided by the project according to published lifecycle data.

Latest release

No releases recorded for this line.

Should I use this version?

Not recommended for new deployments

Upgrade to a currently supported release line. Recommended target: MongoDB 8.0.

Upgrade options

Newer supported MongoDB version lines from CompatHub lifecycle data. Compatibility and security context use existing evidence only.

You are on MongoDB 3.2

End of lifeEOL 30 September 2018

Supported upgrade options

Open full upgrade planner for MongoDB 3.2

Version comparison

Compact comparison against the nearest relevant release lines.

3.28.0
Statusend of lifestandard support
Latest release8.0.29
EOLSept 2018Oct 2029
Riskhighlow

Sources

Where this information comes from.

Lifecycle sources

Release sources

Data coverage

Last checked = last successful upstream check. Latest source update = when upstream content last changed.

Releases tracked
0
Lifecycle periods
2
EOL
Known
Provenance records
3
Data last checked
1 Sept 2026
Latest source update
1 Sept 2026

Other MongoDB versions