IT teams are drowning in alerts, and the ones that get missed can turn into outages. Governable autonomous IT changes that. At @Microsoft Ignite, we’re showing what it looks like in practice: an alert from Azure Monitor goes to an AIOps agent in ServiceNow, which diagnoses the issue. ServiceNow ITSM and the Azure SRE agent then work out the fix together, while IT stays in control of what happens next. Policies are set before agents act, and every action is recorded, including handoffs between ServiceNow and Microsoft agents. Learn more: http://newsroom.servicenow.com/press-releases/details/2026/Microsoft-Ignite-ServiceNow-delivers-governable-autonomous-IT-to-Azure
ServiceNow outages and problems
User reports, last 24 hours
288 reports in total, counted in 15-minute windows
In the last hour, 13 problem reports came in for ServiceNow, and at this time of day there are usually almost none. Over the last 24 hours there were 288 reports. Worldwide, most recent reports were about website (79%) and app (13%). The last spike in reports was 2 h ago and lasted 24 min. These are user reports from the US, where most people report ServiceNow problems.
Around the world right now: normal in 71 other countries. Most reports in the last hour: India 2 · Brazil 1 · Croatia 1. By country
- NormalClose to the usual level22 h · 200 reports
- ElevatedMore than 1.5 times the usual level1 h 15 min · 52 reports
- OutageMore than twice the usual level and far above the day's average45 min · 36 reports
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 288 user reports came in for ServiceNow. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 96.88% uptime for the day.
The most recent spike big enough to count as an outage was 2 hours ago. The busiest 15-minute window of the day had 12 reports, about 7 hours ago.
-
Outage
Ended 2 h agoLasted 15 min12peak reports
-
Outage
Ended 3 h agoLasted 30 min12peak reports
-
Elevated reports
Ended 5 h agoLasted 1 h 15 min11peak reports
-
Outage
Ended 7 h agoLasted 15 min12peak reports
ServiceNow in November 2026
- Problem reports in November
- 1,985
- Outage spikes
- 11
- Periods of elevated reports
- 1
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for ServiceNow worldwide.
Share of 24 recent reports that said what was wrong, from every country listed below.
ServiceNow reports around the world
In the last 24 hours, 452 problem reports about ServiceNow came in from 23 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 19 | 380 |
| India | Normal | 2 | 15 |
| Brazil | Normal | 1 | 10 |
| Croatia | Normal | 1 | 1 |
| Canada | Normal | 0 | 9 |
| The UK | Normal | 0 | 8 |
| Japan | Normal | 0 | 5 |
| New Zealand | Normal | 0 | 4 |
| Mexico | Normal | 0 | 3 |
| Germany | Normal | 0 | 3 |
| The Philippines | Normal | 0 | 2 |
| The Netherlands | Normal | 0 | 1 |
Each country's status compares its reports with the usual level there. 60 more countries had 11 reports in the last 24 hours. Map outlines: Natural Earth.
ServiceNow problem spikes, last 30 days
In the last 30 days, ServiceNow had 12 outage spikes and 1 period of elevated reports. The longest lasted 5 h 7 min, on 16 November.
- Tue 20 Oct: 0 reports
- Wed 21 Oct: no data
- Thu 22 Oct: 0 reports
- Fri 23 Oct: 0 reports
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 0 reports
- Tue 27 Oct: 0 reports
- Wed 28 Oct: 15 reports
- Thu 29 Oct: 67 reports
- Fri 30 Oct: 44 reports (outage spike that day)
- Sat 31 Oct: 13 reports
- Sun 1 Nov: 1 report
- Mon 2 Nov: 17 reports
- Tue 3 Nov: 41 reports
- Wed 4 Nov: 35 reports
- Thu 5 Nov: 44 reports
- Fri 6 Nov: 20 reports
- Sat 7 Nov: 4 reports
- Sun 8 Nov: 6 reports
- Mon 9 Nov: 49 reports
- Tue 10 Nov: 44 reports
- Wed 11 Nov: 42 reports (outage spike that day)
- Thu 12 Nov: 435 reports (outage spike that day)
- Fri 13 Nov: 112 reports
- Sat 14 Nov: 91 reports (outage spike that day)
- Sun 15 Nov: 18 reports
- Mon 16 Nov: 738 reports (outage spike that day)
- Tue 17 Nov: 288 reports (outage spike that day)
- Wed 18 Nov: no data
-
Outage
Tue 17 Nov, 21:44–22:08Lasted 24 min14peak reports
-
Outage
Tue 17 Nov, 20:38–21:08Lasted 30 min13peak reports
-
Outage
Tue 17 Nov, 18:23–19:38Lasted 1 h 15 min15peak reports
-
Outage
Tue 17 Nov, 17:18–17:47Lasted 29 min14peak reports
-
Elevated reports
Tue 17 Nov, 16:09–16:50Lasted 41 min10peak reports
-
Outage
Mon 16 Nov, 21:36–22:09Lasted 33 min14peak reports
-
Outage
Mon 16 Nov, 20:30–21:09Lasted 38 min12peak reports
-
Outage
Mon 16 Nov, 19:37–20:03Lasted 26 min12peak reports
5 earlier spikes in this period.
By country
In the last 22 days, most ServiceNow problem reports came from the US (1,933), Brazil (94) and India (94). The US had the most days at outage level: 2 of 22. The latest outage spike was on Monday 16 November, in the US.
- The US2 outage days1,933
- BrazilNo spikes94
- IndiaNo spikes94
- The UKNo spikes89
- CanadaNo spikes86
- JapanNo spikes70
- MexicoNo spikes38
- PolandNo spikes32
- Outage spike
- Elevated reports
- Normal
- No data yet
Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 28 October 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. Monthly reports for all services
How to fix ServiceNow not working
ServiceNow is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach servicenow.com over your own connection, right now. Nothing is sent to us or stored.
Check the official status page
Open the official status page and look for an active incident that affects your region or product. If one is listed, wait for the next update before you change your password or open a case.
Try a private window
Open your instance in a private or incognito window and sign in again. If it loads there, clear cookies and cached files only for the instance domain in your normal browser. That isolates the browser.
Confirm your sign-in route
If your organization signs in through SSO, start from the identity provider portal and launch the app from its tile rather than the instance URL. Ask your admin whether your account is locked or your role changed; those account states can break one person while others keep working.
Clear site data, then send details
Remove cookies and cached files for the instance domain, close every tab for it, and sign in once more. If the failure stays, record the time, the page, any on-screen message, and whether another browser or network shows the same result, then give that to your internal admin or open a case with the help centre.
While ServiceNow is down: what to use instead
- IT service desk phone line Call your company's help desk number when the portal won't load; most service desks keep a phone line open for outages and can take your details by hand.
- Now Mobile app Try the mobile app if only the browser is failing.
- A quick written note Write down what broke and the exact error text you saw, so you can file a complete ticket in one go once the instance recovers.
- ServiceNow help centre If you are an instance admin, open a case through the help centre so ServiceNow support knows your instance is affected, although a wide outage can slow that site down as well.
Fix ServiceNow on Windows, Mac, Android and iPhone
ServiceNow on Windows
- Fix
- Clear your browser cache and cookies, or try accessing ServiceNow in an Incognito window to resolve loading issues. You can also flush your DNS cache through your system settings to reset your connection.
- Check
- Verify if ServiceNow is down by attempting to load the portal in a different web browser. You can also check the official ServiceNow Service Status page or contact your organization's IT administrator.
ping servicenow.comTest whether ServiceNow's servers replynslookup servicenow.comCheck that ServiceNow's DNS resolvestracert servicenow.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadServiceNow on Mac
- Fix
- Resolve ServiceNow issues on macOS by clearing your browser's history and disabling conflicting extensions. You can also try renewing your DHCP lease in network settings to refresh your connection.
- Check
- Check if ServiceNow is down by testing the URL in a private Safari window. If the page fails to load, verify your network connection or check the ServiceNow status dashboard.
ping -c 4 servicenow.comTest whether ServiceNow's servers replynslookup servicenow.comCheck that ServiceNow's DNS resolvestraceroute servicenow.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadServiceNow on Android
- Fix
- Fix the ServiceNow app on Android by clearing its cache and data in your device's app settings. You can also check the Google Play Store for any pending updates to the app.
- Check
- Determine if ServiceNow is down on Android by attempting to log in via a mobile web browser. If the browser works, the issue may be isolated to the ServiceNow mobile app.
ServiceNow on iPhone and iPad
- Fix
- Resolve ServiceNow issues on iOS by force-closing the app and checking the App Store for updates. If problems persist, reinstalling the ServiceNow app will clear corrupted local data.
- Check
- Check if ServiceNow is down on iOS by trying to access your instance using Safari. If both the app and browser fail to connect, check your company's network status or VPN connection.
Biggest ServiceNow problems so far
-
1
OutageLasted 5 h 7 min79reports in 15 min
-
2
OutageLasted 3 h 59 min57reports in 15 min
-
3
OutageLasted 21 min16reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as ServiceNow
In the last 30 days, all 13 of ServiceNow's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Chase13 times
- Wells Fargo12 times
- GOV.BR12 times
- ADP12 times
- Microsoft Copilot12 times
- GitHub12 times
How many of ServiceNow's spikes overlapped one of theirs.
During the latest spike
ServiceNow: Tue 17 Nov, 21:44 to 22:08
- Microsoft Outlook, outage,12 Nov 17:42 to 18 Nov 00:08
- Microsoft 365, outage,12 Nov 17:59 to 18 Nov 00:08
- YouTube, outage,16 Nov 14:42 to 18 Nov 00:08
- Bank of America, outage,16 Nov 15:26 to 18 Nov 00:08
- Chase, outage,16 Nov 15:26 to 18 Nov 00:08
- US Bank, outage,16 Nov 16:06 to 18 Nov 00:08
- Wells Fargo, outage,16 Nov 16:33 to 18 Nov 00:08
- Navy Federal Credit Union, outage,16 Nov 19:15 to 18 Nov 00:08
223 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report ServiceNow problems
The busiest hour for reports about ServiceNow is 19:00 to 20:00 Central European time, and the busiest day is Tuesday.
By hour of the day
- 00:00 to 01:00: 1.3 reports on an average day
- 01:00 to 02:00: 0.63 reports on an average day
- 02:00 to 03:00: 0.48 reports on an average day
- 03:00 to 04:00: 0.59 reports on an average day
- 04:00 to 05:00: 0.26 reports on an average day
- 05:00 to 06:00: 0.8 reports on an average day
- 06:00 to 07:00: 0.61 reports on an average day
- 07:00 to 08:00: 0.32 reports on an average day
- 08:00 to 09:00: 0.17 reports on an average day
- 09:00 to 10:00: 0.24 reports on an average day
- 10:00 to 11:00: 0.1 reports on an average day
- 11:00 to 12:00: 0.18 reports on an average day
- 12:00 to 13:00: 0.43 reports on an average day
- 13:00 to 14:00: 0.53 reports on an average day
- 14:00 to 15:00: 0.58 reports on an average day
- 15:00 to 16:00: 1.8 reports on an average day
- 16:00 to 17:00: 1.5 reports on an average day
- 17:00 to 18:00: 2.1 reports on an average day
- 18:00 to 19:00: 1.8 reports on an average day
- 19:00 to 20:00: 2.3 reports on an average day
- 20:00 to 21:00: 2.1 reports on an average day
- 21:00 to 22:00: 1.5 reports on an average day
- 22:00 to 23:00: 1.1 reports on an average day
- 23:00 to 00:00: 1.5 reports on an average day
By day of the week
- Monday: 28 reports on an average Monday
- Tuesday: 38 reports on an average Tuesday
- Wednesday: 17 reports on an average Wednesday
- Thursday: 31 reports on an average Thursday
- Friday: 27 reports on an average Friday
- Saturday: 15 reports on an average Saturday
- Sunday: 4.1 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 41 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when ServiceNow goes down
ServiceNow is a cloud platform for IT, HR, customer service and operations workflows at large organizations, and US enterprises and agencies rely on it for incidents, approvals, service requests and change records. An outage interrupts the queues and portals people use to report problems or approve changes, and it leaves records stuck without updates.
Access tends to fail first: the login page stalls or single sign-on loops, so you cannot reach incident, request, change or problem records. If you are already inside, forms may hang on submit and approvals stop routing; dashboards can load stale data and integrations with email or asset tools can fail too. Because each customer runs on its own instance, problems often hit one company or one region, and sometimes only a few modules. The official status page and help centre are the places to check for a known instance issue or planned maintenance.
ServiceNow IP address, servers and network
- IPv4 addresses
- 2.16.1.152
Show all 2
- 2.16.1.235
- IPv6
- Not offered
- Network
- AS20940 · Akamai International B.V., registered in the Netherlands
- Served through
- Akamai
- DNS hosted by
- Akamai
- HTTPS certificate
- Issued by Amazon, valid until 7 Apr 2027 (140 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 533 ms (it turned away our automated check, which is common)
Checked from our server in Frankfurt, Germany, 10 h ago, for www.servicenow.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from www.servicenow.com. Every answer turned the automated check away (HTTP 403), which many sites do with bots; the site itself was up. Fastest from Warsaw (18 ms), slowest from Los Angeles (453 ms). Every location connected through Akamai International B.V. (AS20940), using 12 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 403 | 60 ms | 184.86.103.199 |
| ViennaAustria | Up · HTTP 403 | 77 ms | 88.221.92.54 |
| MilanItaly | Up · HTTP 403 | 51 ms | 2.19.124.143 |
| ParisFrance | Up · HTTP 403 | 50 ms | 96.16.248.169 |
| AmsterdamNetherlands | Up · HTTP 403 | 291 ms | 95.100.107.91 |
| MadridSpain | Up · HTTP 403 | 47 ms | 23.211.135.144 |
| WarsawPoland | Up · HTTP 403 | 18 ms | 23.47.124.140 |
| DallasUSA | Up · HTTP 403 | 30 ms | 23.211.127.9 |
| Los AngelesUSA | Up · HTTP 403 | 453 ms | 173.222.162.158 |
| São PauloBrazil | Up · HTTP 403 | 24 ms | 2.18.20.144 |
| SingaporeSingapore | Up · HTTP 403 | 29 ms | 23.32.39.149 |
| TokyoJapan | Up · HTTP 403 | 29 ms | 23.192.47.42 |
Checked with check-host.net from its servers in these cities 10 h ago, for www.servicenow.com. Time is how long each server took to load the page.
ServiceNow FAQ
Is ServiceNow down right now?
Why does ServiceNow keep returning me to the login screen?
Why do I get "You are not authorized to access this record" in ServiceNow?
Why won't the ServiceNow Agent app connect to my instance?
Why can't I approve a request from the ServiceNow mobile app?
Service updates from @servicenow
No posts about problems from @servicenow in the last 14 days. The latest is from .
Contact ServiceNow support
- Official status pagestatus.service-now.com
- Help centresupport.servicenow.com
- Contact formservicenow.com/contact-us.html
- Websiteservicenow.com
- X (Twitter)x.com/servicenow
Tip: when ServiceNow is down, its official status page is the quickest way to confirm the cause and see when a fix is expected.
About ServiceNow
- Category
- Enterprise Software
- Country
- United States
How we track ServiceNow
The status on this page comes from user-submitted problem reports for ServiceNow, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for ServiceNow, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from ServiceNow's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.