ServiceNow Release Cycle 2026: Zurich, Australia, Brazil Timeline
The release names you need to plan around, when they ship, what each family adds, and how to keep N-1 compliance through the cycle without surprises.
How ServiceNow Names Releases
ServiceNow names each major release family alphabetically. The names were cities through Zurich (2025); once the alphabet ran out at Z, ServiceNow restarted at A with country names. Australia reached general availability on May 5, 2026, after early availability opened on March 12, 2026. Patch releases inside a family arrive regularly through the life of that family.
The named family is what people mean when they say "we are on Zurich" or "we are upgrading to Australia." What they usually skip is which patch level, which Store apps are pinned, and which plugins are dependent on a specific family. All three matter for upgrade planning.
This article gives you the practical timeline, the rough planning windows, and the upgrade checklist that keeps you inside the N-1 compliance window every cycle.
The 2026 and 2027 Family Timeline
ServiceNow publishes exact dates as each family approaches availability. With Zurich, ServiceNow exhausted the city alphabet and switched to country names from Australia onward. Use the table as a planning baseline and confirm future names and GA dates against the official Release Notes when they publish.
| Family | Window | N-1 Window Closes | Notes |
|---|---|---|---|
| Zurich | GA September 10, 2025 | When the family after Australia ships | N-1 while Australia is the current family. |
| Australia | EA March 12, 2026; GA May 5, 2026 | When the next family ships | Current family after May 5, 2026. |
| Next country family | Expected second-half 2026 window | When the following family ships | Confirm name and dates in ServiceNow Release Notes. |
| Following country family | Expected first-half 2027 window | When Denmark ships | Planning assumption only until ServiceNow publishes the release. |
| Later country family | Expected second-half 2027 window | When the next family ships | Confirm at release-note publication time. |
If you are on Zurich while Australia is current, you are on N-1. Zurich becomes N-2 when the next family after Australia becomes current, so Zurich customers should plan and test the move to Australia before that next GA window.
Patch Release Cadence Inside a Family
Each named family receives patch releases every four to six weeks until the next family ships. The pattern is consistent:
- GA patch: ships at family GA.
- Patch 1, 2, 3: bug fixes and small enhancements at four to six week intervals.
- Patch hot fixes: emergency patches for critical security or regression issues, on demand.
- Final patch: the last stabilization patch before the family stops receiving updates.
Customers who stay on the latest patch in their current family enjoy the fewest surprises. The 500+ checkpoints in Instance Audit treat outdated patch levels as a finding, even when the family itself is supported.
Aligning Your Calendar to the Cycle
Two upgrades a year is achievable for most enterprise customers with a disciplined cadence. The window that works is:
| Cycle Stage | Weeks Before GA | Activity |
|---|---|---|
| Pre-read | T-12 | Read Release Notes. Identify deprecations. Run an Upgrade Readiness Agent pre-scan. |
| Backlog | T-10 | Remediate the high-risk findings. Yeti Build Agent drafts refactors against the 42 artifact classes in scope. |
| Sub-prod upgrade | T-6 | Upgrade the dev and test instances. Re-run the agent. Diff against the pre-scan. |
| Regression | T-4 | ATF regression, performance test, full instance audit. |
| CAB | T-2 | Change control. Submit the scored audit report as evidence. |
| Production | T-0 | Upgrade production. Run the agent one more time to confirm parity with sub-prod. |
That is roughly 12 weeks per cycle, twice a year. Done as a cadence rather than a project, it consumes a sustainable share of platform team capacity. For the full N-1 strategy, see the N-1 compliance guide.
What Changes Each Family
Each family ships a mix of three things: new features, deprecations, and quality improvements. The relative weight shifts by family. Recent family-level themes have included:
- Now Assist and AI Agents. Every recent family has expanded the platform's native AI surface.
- Workflow Studio. Flow Designer evolution and Workflow Studio integration are continuous themes.
- UX modernization. Next Experience continues to expand at the expense of UI16 patterns.
- Platform Analytics. Reporting and dashboard primitives shift family by family.
- Security baselines. The default ACL and audit set tightens with each release.
SnowCoder supports Zurich and later families, so anything you build with Yeti AI Chat or the Yeti Build Agent is grounded in the target family's patterns and checked before deployment. See the Yeti Build Agent overview for the 291-story benchmark methodology.
Common Mistakes
- Treating upgrades as projects. They are a cadence. Project economics collapse when the project repeats twice a year.
- Skipping the patch level. Being on Zurich is not enough. Be on the latest patch of Zurich.
- Trusting unmanaged Store apps. Pinned versions are an upgrade blocker. Track which apps support the inbound family before T-12.
- Ignoring deprecations. A deprecation in Australia is a removal in Brazil. Plan two cycles ahead.
- Running production cutover with no pre-scan. The Upgrade Readiness Agent pre-scan is the cheapest insurance in the cycle.
Related Reading
Plan your next upgrade with confidence
Run the Upgrade Readiness Agent on your current family. Get a scored audit report and a remediation backlog before you commit to a date.