Skip to main content
ServiceNow logo

Is ServiceNow Down?

No — ServiceNow is up

Reachable from all 8 checked regions

Average response time: 481ms

Last checked · checks run every 6 hours

Official status page: https://status.service-now.com

ServiceNow uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

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

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

lax
302ms
DNS 75ms TCP 62ms TLS 68ms TTFB 299ms
lhr
312ms
DNS 22ms TCP 82ms TLS 87ms TTFB 310ms
nrt
578ms
DNS 10ms TCP 177ms TLS 183ms TTFB 575ms
ord
163ms
DNS 62ms TCP 20ms TLS 25ms TTFB 160ms
sin
1273ms
DNS 100ms TCP 239ms TLS 245ms TTFB 1268ms
sjc
287ms
DNS 41ms TCP 71ms TLS 76ms TTFB 285ms
syd
783ms
DNS 127ms TCP 207ms TLS 212ms TTFB 780ms
yyz
150ms
DNS 59ms TCP 18ms TLS 23ms TTFB 147ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Okta
Okta
Jira
Jira
Salesforce
Salesforce
PagerDuty
PagerDuty

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.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when ServiceNow goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required