endoflife.ai
EOL Checker Products EOL Watch Get Support

IBM AIX End of Life: "We Run 7.3" Is Not a Support Status — the Technology Level Clock, and the November 30 Deadline

Published: August 11, 2026  ·  EOL Watch — deadline coverage  ·  Dates verified against IBM's AIX support lifecycle page (document 670775, modified July 18, 2026), IBM's AIX Service Strategy white paper, and our tracked lifecycle data — methodology

Ask most teams what AIX they run and you get a release number: "We're on 7.3." Ask IBM what it supports and you get a different unit entirely. AIX support expires per Technology Level — the second field in oslevel -s — and each Technology Level lives about three years. Right now that distinction is worth exactly 111 days: AIX 7.3 TL2 reaches End of Fix Support on November 30, 2026, while a box on 7.3 TL4 keeps receiving fixes to the end of 2028. Same release. Same "we run 7.3." Two years apart in support reality.

The policy is published, precise, and rarely read. Per IBM's AIX Service Strategy: new Technology Levels generally ship once a year in the fall, and "they are supported by fixes provided through Service Packs and iFixes for 3 years." Releases are a much longer clock — shipped roughly every four years and "supported for usage and debug for 10 years under standard SWMA, plus 3-5 years of optional, separately priced, extended support." The release keeps you entitled to open a case. The Technology Level decides whether anything gets fixed.

And IBM's own AIX support lifecycle page is blunt about what End of Fix Support means: "Fix Packs, Service Packs (SPs), and interim fixes will not be created for a TL after the EoFS." That includes security interim fixes — when IBM publishes a security bulletin for AIX, the proactive iFixes cover the latest Service Packs of each active Technology Level. A TL past its End of Fix Support date is outside that machinery entirely, no matter how alive AIX 7.3 itself is.

The AIX 7.3 clock, per IBM's lifecycle page: TL0 — fix support ended December 31, 2024. TL1 — ended December 31, 2025. TL2 — ends November 30, 2026 (111 days from publication). TL3 — ends December 31, 2027. TL4 (shipped December 2025) — ends December 31, 2028. If oslevel -s starts with 7300-02 or lower, the machine stops receiving fixes this year or already has — and the remedy is a TL update, not a migration.

How the AIX lifecycle actually works

AIX levels are named RELE-TL-SP-BBBB — release, Technology Level, Service Pack, build sequence identifier — and oslevel -s prints where a system stands. Three clocks run at once, and confusing them is how "fully supported" estates quietly go unpatched:

The release clock (10+ years). AIX 7.3 shipped December 2021; IBM has published no End of Service date for it, and per policy none of its Technology Levels' expiries change that. Release End of Service is what ended AIX 7.1 on April 30, 2023 — the only date on IBM's TL lifecycle page marked "(EOS)". When a release reaches EOS, everything on it needs either a migration or a paid Service Extension.

The Technology Level clock (3 years). This is the one that bites. Each TL gets Service Packs and interim fixes for about three years from its ship date, and then — per IBM's wording — fixes "will not be created" for it. Usage and debug support continues until the release's EOS: IBM will still help you troubleshoot a dead TL, but the outcome of that troubleshooting cannot be a new fix for your level.

The Service Pack clock (months). Even inside an active TL, currency matters: IBM's proactively published security iFixes target systems "running one of the latest 3 Service Packs of each active Technology Level," and iFixes for earlier Service Packs are by-request. Service Packs land roughly twice a year on the newest TL — so being a year of SPs behind means security relief arrives slower, if at all.

The honest summary: an AIX system is supported when its release is pre-EOS and its Technology Level is inside the three-year fix window and its Service Pack is recent. The first condition holds for every 7.3 box on the planet. The second is the one nobody is watching — which is why this page exists.

Running AIX past its fix window?
Extended support past the official EOL date exists for many products in this position — whether it covers your AIX level is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Every AIX Technology Level's dates

Every Technology Level we track, newest first, with live status. Dates are from our tracked lifecycle data, cross-checked against IBM's AIX support lifecycle page on August 11, 2026. Each level links to its lifecycle page with live status and risk score.

Technology LevelStatusReleasedEnd of Fix Support (EOL)Notes
AIX 7.3 TL4SupportedDec 6, 2025Dec 31, 2028Newest TL — the longest runway on 7.3; next Service Pack targeted February 2027.
AIX 7.3 TL3SupportedDec 6, 2024Dec 31, 2027Serviced; next Service Pack targeted August 2026. First TL under IBM's simplified SP numbering.
AIX 7.3 TL2WarningNov 30, 2023Nov 30, 2026111 days left at publication. No further Service Packs planned — final SP is 7300-02-04.
AIX 7.3 TL1EOLDec 31, 2022Dec 31, 2025Fix support ended; usage/debug support continues while the 7.3 release is pre-EOS.
AIX 7.3 TL0EOLDec 31, 2021Dec 31, 2024The 7.3 GA level. Two TL updates behind a serviced level.
AIX 7.2 TL5SupportedNov 30, 2020TBDThe anomaly: no End of Fix Support announced; IBM targets the next Service Pack for December 4, 2026.
AIX 7.2 TL4EOLNov 30, 2019Nov 30, 2022Unpatched for nearly four years — a 7.2 box below TL5 is not "still supported 7.2."
AIX 7.2 TL3EOLSep 30, 2018Sep 30, 2021Fix support ended 2021.
AIX 7.2 TL2EOLOct 31, 2017Oct 31, 2020Fix support ended 2020.
AIX 7.2 TL1EOLNov 30, 2016Nov 30, 2019Fix support ended 2019.
AIX 7.2 TL0EOLDec 31, 2015Dec 31, 2018The 7.2 GA level.
AIX 7.1 TL5EOLOct 31, 2017Apr 30, 2023Release-level End of Service — all of AIX 7.1 ended here; paid Service Extension territory since.
AIX 6.1 TL9EOLNov 30, 2013Apr 30, 2017AIX 6.1's final level — out of standard support for nearly a decade.

Dates from our tracked dataset (verification pass 2026-08-11), cross-checked against IBM's AIX support lifecycle page. IBM's page lists End of Fix Support per TL and notes that release-level End of Service (EOS) dates live separately on the IBM Software Lifecycle page — the 7.1.5 row's April 2023 date is a release EOS, the only one IBM marks that way. "TBD" reflects IBM's own "To be determined" for 7.2 TL5. IBM's TL release dates are published to month precision; day-precision dates in the Released column are from our tracked data.

The 7.2 anomaly — and the 7.1 lesson

AIX 7.2 is not dead, and pretending otherwise would be exactly the kind of error this site exists to prevent. IBM's lifecycle page lists 7.2 TL5's End of Fix Support as "To be determined" and targets its next Service Pack for December 4, 2026 — six years after the TL shipped, double the normal three-year window, and longer-lived than three of 7.3's own Technology Levels. IBM has published no End of Service date for the 7.2 release. A 7.2 TL5 system current on Service Packs is a supported system.

The catch is the same one as everywhere else in this article: that sentence is true of TL5 only. TL4's fixes ended November 30, 2022; every lower 7.2 level died earlier. And an undated reprieve is still a reprieve — "To be determined" means IBM can determine it, and the December 2026 Service Pack target is a scheduled commitment, not a lifecycle promise. Treat 7.2 TL5 as a comfortable place to be current and a bad place to be complacent.

AIX 7.1 shows what the far side looks like. Its release-level End of Service passed on April 30, 2023. Since then, staying patched on 7.1 has meant a paid IBM Software Support Service Extension — IBM's name for what it plainly calls "commonly referred to as extended support," sold for End of Service versions of AIX, AIX Licensed Program Products, and PowerVM through IBM Business Partners and sales representatives. IBM's service strategy frames the envelope: 10 years of standard support, then "3-5 years of optional, separately priced, extended support." Our IBM enterprise matrix covers what Service Extensions tend to cost relative to standard support; the short version is that they are a bridge you buy by the year, not a destination.

Who this lands on — and why the stakes are compliance-shaped

AIX on Power is not general-purpose infrastructure anymore; what remains is the load-bearing core — banking ledgers, insurance policy administration, manufacturing ERP and MES, logistics. That concentration cuts two ways. The workloads are the last ones anyone wants to touch, which is how a box quietly rides a Technology Level to its End of Fix Support date. And the organizations running them are precisely the ones with auditors: an EU financial institution answering to DORA's legacy-ICT provisions (in application since January 2025) or an essential entity under NIS2 will find that "the vendor no longer creates fixes for this level" is a finding, not a footnote — regardless of whether the release as a whole is alive. IBM publishing the TL dates makes the status legible to any auditor who looks.

On the exploitation ledger, honesty favors AIX: no IBM AIX entry appears in CISA's Known Exploited Vulnerabilities catalog as of the August 10, 2026 catalog release — we checked before writing this. (The nearest touchpoint is the 2014 GNU Bash "Shellshock" entry, whose vendor notes link an IBM bulletin about the AIX Toolbox's Bash packages — a component CVE, not an AIX listing.) That is a materially better record than most of what we cover. It is not a reason to skip TL updates: IBM ships security interim fixes for AIX regularly, those fixes target active Technology Levels only, and a platform that runs core banking does not need a public exploitation record to justify staying inside the fix window.

The fix is a TL update, not a migration — which is why waiting has no alibi

Here is the structural difference between this deadline and most of the ones we write about. When RHEL 7 or Windows Server 2012 hit end of support, the remedy was a major-version migration — a project measured in quarters, with application recertification, new hardware questions, and real risk. When an AIX Technology Level expires, the remedy is usually a TL update within the same release: plan against IBM's Fix Level Recommendation Tool, take a mksysb (or use alt_disk_install / multibos for a bootable fallback), run smitty update_all, reboot, retest. IBM's own strategy paper describes exactly this path and marks a TL "recommended" about 90 days after its first Service Pack ships. It is a maintenance window, not a program of work.

That is what makes procrastination here uniquely unjustifiable. A team that defers a RHEL-style migration is at least avoiding a real project; a team that lets 7.3 TL2 expire in November is deferring a reboot. The one honest complication is hardware: newer Technology Levels enable — and sometimes require — newer Power hardware support, so estates on old iron should check IBM's system-to-AIX maps before assuming any TL is reachable. For everything else, the November 30 date is the cheapest deadline on this year's EOL calendar to comply with.

The three-step check, today: run oslevel -s on every AIX LPAR (the fleet answer, not the sample answer — NIM and HMC inventories help). Map the second field against the table above. Anything on 7300-02 or below gets a TL update scheduled before November 30; anything on 7.2 below TL5 or on 7.1 gets a harder conversation — Service Extension, or the migration that has been deferred since the last date passed.

We track IBM AIX and 480+ other products against vendor-verified datesevery AIX Technology Level with live status, check any version in seconds, or see what else hits end of life this quarter.

What to do about it

IBM AIX currently carries an EOL Risk Score™ of 40/100 — Grade B, moderate risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the IBM AIX lifecycle page.

The right response comes down to one question: how many more years does this system need to run? For a dead Technology Level on a living release, the answer is almost always the same regardless: take the TL update — it is a maintenance window, not a project. Extended support (IBM's Service Extension) is the tool for End of Service releases like AIX 7.1 — and even there it is priced as a bridge, not a destination. If the workload must run indefinitely, the TL update buys time to plan the eventual release migration on your schedule instead of IBM's.

Frequently Asked Questions

When does AIX 7.3 reach end of life?

IBM has not announced an End of Service date for the AIX 7.3 release — under IBM's published service strategy, AIX releases are supported for usage and debug for 10 years under standard SWMA, plus 3 to 5 years of optional, separately priced extended support. What does expire is each Technology Level: per IBM's AIX support lifecycle page, AIX 7.3 TL2 reaches End of Fix Support on November 30, 2026, TL3 on December 31, 2027, and TL4 on December 31, 2028. TL1 and TL0 are already past theirs (December 31, 2025 and December 31, 2024). To keep receiving fixes, you must stay on a Technology Level inside its three-year fix window — the release being alive is not enough.

Is AIX 7.2 still supported in 2026?

Yes — but only on its final Technology Level. AIX 7.2 TL5 (shipped November 2020) is still in service: IBM lists its End of Fix Support as to be determined, with the next Service Pack targeted for December 4, 2026. Every earlier 7.2 Technology Level is done — TL4 stopped receiving fixes November 30, 2022, and TL0 through TL3 stopped earlier still. So a 7.2 estate is supported only if it is current on TL5; anything below has been unpatched for years. AIX 7.1 is the harder story: its End of Service was April 30, 2023, and continued fixes require a paid IBM Service Extension.

What happens when an AIX Technology Level reaches End of Fix Support?

Per IBM's definition, End of Fix Support is the end of the maintenance period for a TL — Fix Packs, Service Packs, and interim fixes will not be created for that TL after the date, and that includes the security interim fixes IBM publishes when an AIX vulnerability is fixed. Usage and debug support continues until the release itself reaches End of Service, so IBM will still take the call and help diagnose — but nothing new gets fixed. The remedy is usually a Technology Level update within the same release — an update_all to a serviced TL and a reboot in a maintenance window — not an operating system migration.

Does IBM sell extended support for AIX?

Yes. IBM offers Software Support Service Extensions — commonly referred to as extended support — for End of Service versions of the AIX operating system, AIX Licensed Program Products, and PowerVM, purchased through an IBM Business Partner or IBM sales representative. IBM's service strategy describes releases as supported for 10 years under standard SWMA plus 3 to 5 years of optional, separately priced extended support; AIX 7.1, out of standard support since April 30, 2023, is the current example. Note what Service Extensions do not cover: they apply to End of Service releases, not to skipped Technology Levels inside a supported release — a dead TL on a live release is fixed by a TL update, not a contract.

Related

The Monthly EOL Digest™

Once a month — critical EOL dates, CVE blind spots, and lifecycle changes worth knowing.

© 2026 endoflife.ai · How we verify our dates · API · About · Data from endoflife.date (MIT)