Skip to main content
ServiceNow logo

Is ServiceNow Down?

No — ServiceNow is up
ServiceNow's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 329 ms

Right now

We could not read ServiceNow's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

signon.service-now.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
329 ms
Checked

By region

  • Amsterdam reachable, 357 ms
  • Dallas reachable, 295 ms
  • Frankfurt reachable, 309 ms
  • Newark reachable, 69 ms
  • Paris reachable, 349 ms
  • Stockholm reachable, 527 ms
  • São Paulo reachable, 505 ms
  • Toronto reachable, 222 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam57 ms87 ms92 ms356 ms
Dallas72 ms59 ms63 ms295 ms
Frankfurt6 ms88 ms93 ms309 ms
Newark12 ms9 ms13 ms69 ms
Paris55 ms79 ms84 ms349 ms
Stockholm149 ms111 ms116 ms526 ms
São Paulo118 ms116 ms122 ms505 ms
Toronto137 ms16 ms21 ms222 ms
We check that signon.service-now.com loads, not every feature behind it. Test it yourself

History

ServiceNow website availability

Measured by FlareWarden · signon.service-now.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
450ms

Last 30 days

66-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 28 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of signon.service-now.com from multiple regions every 6 hours. ServiceNow's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 66 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What ServiceNow does

ServiceNow is an enterprise workflow platform most widely used for IT service management: incident tickets, change requests, the service catalogue and the employee help desk. Large organisations also run HR cases, security response and asset management on it. Each customer gets a named instance hosted in a specific ServiceNow datacenter rather than a single shared address.

What an outage looks like

Your instance address stops loading or hangs part-way through, and agents cannot open, update or close tickets. Because instances are tied to a datacenter, colleagues on a different instance often see nothing wrong at all. Integrations that push records in through the Table API fail quietly, so alerts from monitoring tools stop becoming incidents while the tools themselves stay healthy.

What to do about it

Open status.service-now.com and find your datacenter on the availability map rather than reading a global headline, because the page reports each datacenter region separately. It also tracks Now Support, the Developer site and the Store as their own entries, so documentation or the app store can fail while instances are fine. Confirm which datacenter hosts your instance before escalating.

Is it down for everyone, or just you?

If this page says ServiceNow is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

ServiceNow outage FAQ

ServiceNow says available but my instance is down. Why?
The status page is organised by datacenter region, not by instance. Your instance lives in one datacenter, so an incident there can leave every other region reporting available. Find the datacenter your instance is hosted in and read that entry. If the map shows your region healthy and the instance still fails, it is more likely an instance-specific problem and belongs in a Now Support case.
Is ServiceNow down for everyone or just my company?
Usually just some customers. ServiceNow runs many datacenters and each instance sits in one of them, so a single incident rarely touches the whole customer base. That is different from a shared SaaS product where one outage hits everyone. Ask a contact at another company on a different instance, or check whether your datacenter specifically is flagged.
Do tickets get lost during a ServiceNow outage?
ServiceNow does not publish retry behaviour for inbound integrations on its status page, so we will not claim records are queued. Treat anything your monitoring tools or email integrations tried to push during the window as unconfirmed, and reconcile against the source system afterwards rather than assuming the ticket exists.
Does a ServiceNow outage affect the developer site and the Store?
Not necessarily. The status page lists Now Support, Developer and Store as their own entries alongside the datacenter map. Documentation, the developer instance signup and app downloads can be interrupted while production instances keep running, and the reverse happens too. Check the specific entry for whichever surface you are trying to reach.
Can I still work while ServiceNow is unavailable?
Record work offline and reconcile later. Note incident details, timestamps and who was contacted in whatever channel your team already uses, then enter them once the instance returns. Avoid re-submitting the same change request repeatedly during an outage; duplicate change records are harder to untangle afterwards than a late one.

How we measure this

  • We request ServiceNow's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where ServiceNow publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of ServiceNow itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when ServiceNow goes down

We check ServiceNow every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required