Ubuntu LTS or interim for server: which one better?
Ubuntu interim release na 9 months support, while LTS get 5 years of security updates. See the upgrade cost before you put either one for server.
Ubuntu LTS vs interim releases: short answer
To choose between Ubuntu LTS and interim release for server, na one number matter: how long that release go continue to get security updates. LTS dey get five years of standard security maintenance. Interim release dey get nine months, then the updates go stop, so you must upgrade or rebuild. Run LTS for anything wey other people depend on. Run interim release only where you fit rebuild without asking anybody.
LTS mean long term support. Canonical dey publish one LTS every two years, for April of even years, and one interim release every six months between dem. 26.04 LTS shipped on 23 April 2026, and its standard security maintenance go continue reach 2031. 26.10 was released on 15 October 2026, and na interim release, so its clock go stop for July 2027.
How long dem support each Ubuntu release
Di data wey dey behind dis chart
[
{
"label": "LTS, standard support",
"support_months": 60,
"upgrades_over_5_years": 1
},
{
"label": "LTS with Ubuntu Pro",
"support_months": 120,
"upgrades_over_5_years": 0
},
{
"label": "Interim release",
"support_months": 9,
"upgrades_over_5_years": 10
}
]Na Canonical publish these policy figures as of October 2026, no be measurements from test box. LTS get 60 months of standard security maintenance, meaning say e get 1 planned release upgrade within five years. Interim release get 9 months. If you remain on interim track for the same five years, you go pay with 10 release upgrades, because you no fit skip release and five years contain ten of dem.
Ubuntu Pro subscription increase the LTS figure to 120 months, wey be ten years, and e add the universe repository to the main coverage wey LTS already get. Canonical legal description of Pro name those two: Main through esm-infra and Universe through esm-apps. As of October 2026, Canonical personal terms make Pro free for up to five physical Ubuntu systems, with unlimited VMs or containers on top of dem. The terms no explain how VPS wey you rent on another person hardware go count, so read dem before you attach a fleet. Interim release no get equivalent. Nine months na the complete offer, and no subscription fit extend am.
Wetin nine months dey cost for real server
Make we use 26.10 as example. E release on 15 October 2026, and e security maintenance go end for July 2027, just like the same nine-month pattern wey end 25.10 for July 2026. If you look am as calendar, e go look like say you get one maintenance window every three quarters. But that calendar reading no correct, and e wrong for the side wey go cost more.
How the deadline chain dey work
Install 26.10 for October 2026 and wait until the last safe time. You upgrade go 27.04 for June 2027, just before 26.10 support finish. But 27.04 release for April 2027, and e own nine months go finish for January 2028. Your second deadline go come seven months after the first one, no be nine.
Upgrade again for December 2027 go 27.10, wey release for October 2027 and go finish for July 2028. From here, the pattern don set. You dey always one release behind the current one, so deadline go land about every six months. Nine months na the support length for one release. E no be the gap between your maintenance windows.
Release upgrade dey replace the operating system for the same machine. do-release-upgrade dey rewrite the apt sources, disable third party repositories, change the version of almost every installed package, stop to ask about config files wey you don edit, then reboot at the end. Na why you need plan am as maintenance window, no be background job.
If you run am over ssh, the tool go protect you if your connection drop. E go start e own screen session and open another sshd, then tell you first:
To make recovery in case of failure easier, an additional sshd will
be started on port '1022'. If anything goes wrong with the running ssh
you can still connect to the additional one.Allow am. If your firewall or your provider separate network firewall block 1022, that fallback no go dey available. But connection wey drop still no go stop the upgrade. E go continue inside the screen session. When you ssh back in and run sudo do-release-upgrade again, the upgrader go find e own session and attach back to am instead of starting another upgrade. Port 1022 dey cover the case where sshd for port 22 stop accepting logins halfway through. If 1022 no dey, na provider console go be your way back in. If you run inside tmux or screen by yourself, you get the same protection for any box.
The config file prompts na wetin fit turn fifteen-minute upgrade to one hour:
Configuration file '/etc/ssh/sshd_config'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ?If you keep your file, you fit miss the changes wey the new default get. If you take the maintainer's file, your hardening go disappear until you put am back. No answer safe if you no know wetin change for that release. Na why reading the release notes na part of the maintenance window, no be optional homework.
Then multiply am by the number of boxes. One VPS for interim track na ten upgrade windows inside five years. Five VPS boxes na fifty, unless every box disposable and you rebuild am from an image. Five boxes for LTS track na five upgrades for the same period, and you fit choose the month wey each one go happen.
Why you no fit skip an Ubuntu release
The upgrade paths fixed. An interim release dey upgrade to the next release, no matter which one e be. An LTS dey upgrade directly to the next LTS, or to the next interim release if you request am. Nothing dey go beyond that for one run. To move from 26.10 to 28.04 LTS, you must pass through 27.04 and 27.10, or reinstall the machine.
The mechanism worth knowing, because e show say the rule no go bend. do-release-upgrade dey fetch a meta-release file from changelogs.ubuntu.com, then e download the upgrade tool for the release wey e dey offer. That tool accepts only the starting releases for its supported list and e reject any other one with An upgrade from '...' to '...' is not supported with this tool. Canonical supports exactly two paths: from one interim release to the next, and from one LTS to the next LTS. So, jump outside those paths, like 26.10 straight to 28.04 or 22.04 straight to 26.04, no get tool or support behind am. The upgrader no dey reject am because of caution. Nothing dey there for am to offer.
The release wey you get offered dey come from one config line:
grep -i prompt /etc/update-manager/release-upgrades
sudo do-release-upgrade -cPrompt=lts dey offer only the next LTS. Prompt=normal dey offer the next release, whether na LTS or not. As of 3 November 2026, the meta-release file wey Canonical dey serve still end for 26.04.1 LTS and e no list 26.10, so a 26.04 box with Prompt=normal no go get 26.10 offer yet. Prompt=never no dey offer anything, and na so you fit stop colleague wey mean well from starting upgrade wey you no plan. For release wey no be LTS, lts dey behave exactly like normal, because the next release after 26.10 na 27.04 under both settings. The check dey print Checking for a new Ubuntu release and then a New release ... available. line when something dey available. When nothing dey available, the wording depend on Prompt: with lts e dey print There is no development version of an LTS available. followed by pointer to Prompt=normal, and na only with normal e dey print No new release found.
One more scheduling rule dey catch people. An LTS-to-LTS upgrade no dey get offered on the day the new LTS ships. E opens with the first point release at the earliest. 26.04.1 release on 27 August 2026, and Canonical then hold back the 24.04 upgrade for some more weeks while e backport fixes for regressions in rust-coreutils. A point release no be new version of Ubuntu but the same release with all the updates made so far rolled into new install media, and the wait dey give the upgrade path months of testing before dem offer am to anybody. A 24.04 box with Prompt=lts wey get There is no development version of an LTS available. as answer from the check throughout summer 2026 no break. E dey follow policy. That path don open now: on 29 September 2026 Canonical enable upgrades from 24.04 LTS to 26.04.1 LTS, offered through Update Manager with staggered rollout, and for server sudo do-release-upgrade dey start am immediately. The 24.04 to 26.04 LTS upgrade na the run wey you suppose plan and rehearse now.
When interim release make sense
Na four cases where e genuinely better:
- You need kernel or userspace version wey LTS archive no carry, for this box, now.
- The machine na build host, CI runner, or test box wey you dey rebuild from image, so upgrade na fresh instance instead of maintenance window.
- Hardware or hypervisor feature land after LTS freeze, and no backport dey available.
- You dey check wetin the next LTS go contain. 28.04 dey assembled from 26.10, 27.04, and 27.10, and to find breaking change for spare VPS cost less than to find am for the important box.
Most people wey choose interim release dey need one newer package, no be newer distribution. Two cheaper answers dey. Hardware enablement stack dey bring kernels from later releases enter LTS: for 24.04, na sudo apt install linux-generic-hwe-24.04, and e dey move forward for each point release, starting with the second one. For one application, container image or the vendor own repository fit move one part instead of the whole operating system.
When interim release no be the right choice
- Anything wey get paying users or an on-call rotation. You go accept mandatory upgrade two times every year in exchange for package versions wey you fit never use.
- Any box where unattended-upgrades dey handle your security patching for you. That automation only dey as good as the security repository wey e dey pull from.
- A fleet wey you dey upgrade by hand, because the real cost na one maintenance window multiplied by the number of boxes.
- Anything wey you install and then no check for one year. Interim release wey you forget about go become unpatched internet-facing server nine months later.
That last failure dey quiet, and na wetin make am dangerous. When release reach end of life, its packages move go old-releases.ubuntu.com, so sudo apt update start to fail against archive.ubuntu.com with 404 errors. The package lists for disk go stale. unattended-upgrades continue to run according to its timer and continue to write lines like this inside /var/log/unattended-upgrades/unattended-upgrades.log:
No packages found that can be upgraded unattended and no pending auto-removalsThat line read the same way for server wey get all patches and server wey release don die four months ago. Unless person read the apt errors or track the end of life date, nothing for the machine go tell you which one you dey look at.
Di type change wey go first land for interim track
For March 2026, one Canonical engineer propose for Ubuntu discourse make dem reduce the signed GRUB bootloader wey dey ship for secure boot to only the necessary parts, starting with 26.10. The proposal keep /boot for ext4, FAT and ISO9660, plus squashfs for snaps. E remove filesystem drivers for Btrfs, HFS+, XFS and ZFS, JPEG and PNG image loading, Apple partition tables, and /boot on LVM, software RAID wey no be RAID 1, or inside LUKS encryption. The reason wey dem give be say parsers inside bootloader dey constantly cause security bugs. The change affect only boot path. LVM, RAID, LUKS, Btrfs and ZFS go still work for running system, and full GRUB feature set go still dey available when secure boot dey disabled.
E no ship for 26.10. As of 25 October 2026, 26.10 release notes list am as known issue with heading "Future upgrades might be blocked for unsupported /boot configurations". E talk say for future Ubuntu release, boot loader go remove support for encrypted /boot, RAID-5/6, Apple partition tables, and Btrfs, HFS+, XFS and ZFS. The package wey dey build the EFI images wey dem go sign for 26.10, grub2-unsigned 2.14-2ubuntu1, na the same version wey 26.04 carry, and e still build all those modules together with LUKS, LVM and every md-raid level. Wetin 26.10 get na preparation work: installer dey apply new /boot storage requirements "in preparation for signed GRUB", and release notes talk say work dey go on so release upgrader fit detect affected systems and block upgrade wey no safe.
For most VPS instances, none of this go change anything, because dem dey boot without secure boot from plain ext4 /boot for GPT partition table. Check your own system instead of assuming. If your machine dey boot with secure boot and /boot dey on ZFS, btrfs or XFS, on LVM or RAID, or inside LUKS, na exactly this kind change wey go first meet you for interim track. For that track, you go upgrade into am within months after e land. The proposal itself advise anybody wey depend on the removed features to remain on 26.04 LTS. Canonical release cycle page, as of 3 November 2026, show say Ubuntu Pro and Legacy add-on cover am until May 2041. That advice summarize the whole matter for one sentence. Interim releases na where dem dey test changes. LTS na where those changes arrive after two years of interim releases don show wetin dem break.
The same pattern dey happen for smaller ways for every interim release. Default versions of the database, language runtime and init configuration dey move forward, so config files wey work before fit stop working. Moving defaults forward na the reason interim release dey exist, so reading release notes before each of those ten upgrades na part of the cost wey you agree to pay.
Track wey you go choose when you dey build the box
Choose the track when you dey install am, because to change am afterwards mean say you go reinstall or do plenty upgrades one after another. For new server, four commands go show you where you stand:
lsb_release -a
grep -i prompt /etc/update-manager/release-upgrades
sudo do-release-upgrade -c
pro security-statuslsb_release -a suppose name the release wey you plan install, and for LTS, the description line suppose end with LTS. The Prompt line suppose match the track wey you choose, no be the one wey provider image happen to ship with. do-release-upgrade -c for the newest LTS with Prompt=lts suppose answer There is no development version of an LTS available., and this only mean say newer LTS never dey available yet. For 24.04, e now dey offer 26.04, because that upgrade path open on 29 September 2026. If e offer interim release instead, Prompt don set to normal and person suppose confirm whether na deliberate choice. pro security-status report how many installed packages dey covered by each update stream, and e go clearly talk when machine no dey attached to subscription.
Then write the end of life date for place wey you go see am again, beside the other build notes for that server. This one join the other work for the first ten minutes for new VPS, because support date wey dey only for person memory na the one wey go expire without anybody noticing. If na the six-month churn you dey try avoid completely, FreeBSD release model compared with Linux worth one hour reading before you commit fleet to either one.
FAQ
I suppose make I run Ubuntu interim release for production server?
For almost every case, no. Interim release dey stop receive security updates nine months after e release, so production for that track mean say you must upgrade roughly two times every year, forever. The genuine exceptions na machines wey you dey rebuild from image anyway, like CI runners and build hosts. For dem, upgrade na new instance, no be maintenance window. If real users depend on the machine, install the LTS and use the saved maintenance windows for another work.
How long Ubuntu interim release dey supported?
Nine months. 26.10 release on 15 October 2026, and e security maintenance go end for July 2027. Na the same pattern wey end 25.10 for July 2026. Every interim release follow the same pattern: dem release am for April or October, then support finish nine months later. LTS get five years of standard security maintenance. Ubuntu Pro fit extend am to ten years. As of October 2026, Canonical personal terms make Pro free for up to five physical Ubuntu systems, with unlimited VMs or containers on top of dem.
I fit skip Ubuntu releases when I dey upgrade?
Only from one LTS go the next LTS. do-release-upgrade dey follow fixed paths: interim release go the next release, while LTS fit go the next LTS directly and skip the interim releases between dem. To move from 26.10 go 28.04 LTS, you must first run upgrade through 27.04 and 27.10, or reinstall the machine. Canonical only supports these two sequential paths. The upgrade tool go refuse any starting release wey no dey for its supported list, so no tool dey support any other jump and e no go ever offer am.
Wetin go happen when my Ubuntu release reach end of life?
Its packages go move to old-releases.ubuntu.com, so sudo apt update go start fail against archive.ubuntu.com with 404 errors. No new security updates go publish for that release again. Nothing for the machine go announce this. The server go continue running and serving traffic while every new vulnerability inside am remain open. Recovery na release upgrade wey you run under time pressure, or rebuild. So monitor the date instead of waiting for symptoms.
LTS kernel too old for new hardware?
Usually no, because LTS no dey keep its original kernel for five years. Hardware enablement stack, HWE, dey bring kernels from later releases into the LTS through point releases. Server installation fit opt in with package like linux-generic-hwe-24.04. Check wetin you dey run with uname -r before you assume say kernel na the blocker. If the missing part na userspace version instead of kernel, container or vendor repository na much smaller change than moving the whole machine go interim track.