OBLYTECH Logo
OBLYTECH Logo

How to Find Your ServiceNow Version

The quickest way to find your ServiceNow version is to open the stats page. Add stats.do to the end of your instance address, or open System Diagnostics in the navigator and choose Stats. Note the version details the page shows, as the next sections explain.

You will need to be signed in, because the recommended setting blocks unauthenticated visitors from the stats page. Whether a non-admin account can open it depends on the instance, so if the page refuses you, skip to the last method below.

What “version” means on ServiceNow

People ask for “the version” and mean three different things, so settle which one you need before you go looking.

  • Release family. ServiceNow names each family after a city. The family is the headline version, and it is what compatibility notes, store app listings and upgrade planning refer to.
  • Patch level. Inside a family, patches are issued over time. A move from one family to another is an upgrade. A move from, say, patch 1 to patch 3 within the same family is a patch upgrade. The distinction matters because the effort and risk are different.
  • Hotfix level. Hotfixes are a release type issued alongside patches.

The page you read will usually give you all three at once. The skill is knowing which part of the string answers your question.

Method 1: read the stats page

This needs no navigation and shows the answer on one screen.

  1. Sign in to the instance in a browser with an admin account.
  2. In the browser address bar, add stats.do to the end of the instance address and press Enter. Alternatively, open System Diagnostics in the left navigator and choose Stats, or type stats.do into the navigator filter.
  3. Look near the top of the page for any build or version details, and note what you find.

Treat the build tag as something to read by eye rather than parse with code. Its exact format is not something to rely on across releases, and the tag is most useful when you copy it whole and compare it with another one.

Why the stats page may refuse you

The stats page is a diagnostic page, and it can be restricted through a system property named glide.security.diag_txns_acl. That property controls whether stats.do and a few other diagnostic pages can be reached from an unauthenticated connection. Its recommended value is true, so check yours.

If the page refuses you, use the last method below instead, or have an admin read the value for you.

Method 2: check system properties

If you have admin access and prefer to read the value directly, or the stats page does not open for some other reason, the system properties list may hold version-related values.

  1. Open the system properties list from the navigator.
  2. Search the property list for version-related values and read any that you find.
  3. Compare each value with the stats page, and note any that disagree.

Which version-related properties exist and what they contain varies by instance, so confirm on yours. Treat what you find as a cross-check against the stats page, not as a replacement for it.

Method 3: look at upgrade history

Version questions are often really history questions. You might know the current release but need to know when the instance moved to it, or what it ran before.

  1. Open the upgrade history list from the navigator, or open the list by name in the filter.
  2. Sort by the start or finish time column, if your list shows one, so the newest entry sits first.
  3. Read the From and To values on each row.

This gives you a timeline, which the stats page cannot. It is the better source when you are preparing an audit note, comparing a development instance with production, or checking whether a recent upgrade really finished. If the list shows only a few rows, treat it as the recorded history on this instance, which may not cover every past upgrade.

Method 4: read it from a script

Sometimes a script needs to branch on the version, for example in a fix script that must behave differently across releases. You can read a system property from server-side code, but be careful.

Some system properties exist only once they have been added to an instance, so a property that returns a value on one instance can be missing on another. If you script against it, do these things:

  • Check for an empty result and handle it explicitly rather than assuming a value exists.
  • Test on a sub-production instance that matches the release of production, as set out in this testing strategy guide, before the script goes anywhere near live data.
  • Prefer feature checks, such as testing that a table or field exists, over comparing version strings. A feature check keeps working when the naming of releases changes.

Method 5: ask the platform owner

If you do not have admin access, you do not need to guess. Ask the person who manages the instance, and give them a precise request: the release family, the patch level and the build tag from the stats page. Asking for the build tag rather than “the version” avoids the common outcome where you receive only the family name and later learn that a patch was missing.

Which method to use

Your situation Best method
You are an admin and want a fast answer Stats page
You want a value to copy, or the stats page does not open System properties
You need to know when it changed Upgrade history
A script needs to react to the version Script, with an empty-value guard and ideally a feature check
You have no admin rights Ask the platform owner for the build tag

Common mistakes when checking the version

Reading the family and stopping. Two instances can both be on the same family and still differ by patches. If you are comparing a development instance with production, compare the full build tag.

Confusing instance version with application versions. The platform version and the versions of individual store apps and plugins are separate things. If your question is about an app, look at its own record rather than at the stats page.

Comparing against the wrong instance. Organisations often hold several instances. Confirm the address in your browser before you record anything, since a development instance can sit a release ahead of production while an upgrade is being tested.

Parsing the build tag in code. The temptation is strong because the tag looks regular. It is a string for people to read. Release naming changes, and a parser that works today can fail quietly later.

Trusting a cached screen. If an upgrade finished recently, a browser tab that was open before it can still show the old build. Reload the stats page, or sign out and back in, before you write the number down.

What to do with the answer

Write down the full build tag with the date you read it and the instance name. If you are planning an upgrade, it tells you which release you start from and how many families you cross. The wider upgrade and release readiness guidance covers what comes next. If you are troubleshooting, quote the build tag when you raise a case, because behaviour often differs by patch.

Frequently asked questions

Can I find the ServiceNow version without logging in?

Not reliably. Whether the stats page opens without signing in depends on the glide.security.diag_txns_acl property, and its recommended value is true. A login page may show branding but should not be counted on to show a version. If you cannot sign in, ask whoever administers the instance.

Does a non-admin user see the version?

The recommended setting blocks unauthenticated visitors from the stats page. The property does not say whether a signed-in non-admin account can open it, so check on your instance. If you cannot open it, ask an admin for the build tag.

What is the difference between an upgrade and an update?

An upgrade moves the instance to a different release family. A patch upgrade stays inside one family, for example from one patch to a later patch. Upgrades usually need more testing and compatibility checks because more changes arrive at once.

Why does the build tag look different on my other instance?

Different instances can be on different families, patches or hotfixes, and the tag carries all three. If the two tags differ, the instances are not at the same level, which can explain behaviour that differs between development and production.

Where do I see past upgrades?

Open the upgrade history list. Each row records a move between versions, so you can see what the instance ran before and when it changed.

Is it safe to use the version in a script?

It can work, but some system properties exist only on some instances, so guard against empty values and test on a matching sub-production instance. A feature check is more durable than a version comparison.