Nintex logo

Is Nintex Down?

SaaSLive status, outages, and incident history

No. Nintex is up right now.

Every monitored Nintex system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving

Know the moment Nintex breaks

Nintex is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Nintex status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Nintex Component Status

The main Nintex systems on this page. All 54 are operational right now.

54operational
Nintex Analytics [Australia]
Operational
Nintex Analytics [Canada]
Operational
Nintex Analytics [Europe]
Operational

51 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Nintex Analytics [Japan], Nintex Analytics [Singapore], Nintex Analytics [United Arab Emirates], Nintex Analytics [United Kingdom], Nintex Analytics [United States], Nintex App Studio - Build Services [Australia], Nintex App Studio - Portal [United States], Nintex Automation Cloud [Australia], Nintex Automation Cloud [Canada], Nintex Automation Cloud [Europe], Nintex Automation Cloud [Singapore], Nintex Automation Cloud [United Kingdom], and 39 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Nintex Outages & Incidents

Incident history from the official Nintex status page, including resolution updates.

DocGen for Salesforce failures due to Salesforce's API outageResolved Sep 16, 2026 · 9h 39mResolved

Salesforce services are experiencing a disruption, which is causing document generation requests to fail. Our engineers are actively monitoring the Salesforce incident and tracking updates here: https://status.salesforce.com/incidents/20004433 --- [2026-09-16T10:59:34.008Z] (500) Our investigation indicates that document generation failures are being caused by timeout errors returned from Salesforce due to an ongoing Salesforce API outage. We are tracking the Salesforce incident here: https://status.salesforce.com/incidents/20004433

User management page not loading usersResolved Sep 10, 2026 · 83h 39mResolved

We are currently investigating a problem affecting the user management page not loading users caused by the SCIM endpoint. --- [2026-09-10T16:04:28.467Z] (400) The problem has been identified and fixed and we are actively monitoring to ensure system stability.

Nintex K2 Cloud service maintenanceScheduled for Sep 10, 2026 · 26h 0mScheduled

Scheduled Maintenance

Nintex Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Nintex incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 11 days with incidentsSep 25

Live Nintex Outage Reports

Problems reported by engineers using Nintex. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Nintex problems reported yet.

Something wrong with Nintex on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Nintex

Nintex maintains a public status page at status.nintex.com reporting overall service health. Follow Nintex downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Nintex uptime at 98.86%. Response times, incident history, and SLA tracking for Nintex are available on the PulsAPI dashboard.

Nintex Status FAQ

Is Nintex down right now?

The verdict at the top of this page comes from the latest poll of the official Nintex status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Nintex is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Nintex recovers.

How do I check Nintex uptime history?

PulsAPI tracks Nintex uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 98.86%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Nintex changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Nintex outages?

PulsAPI reads the official Nintex status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Nintex components?

Yes. PulsAPI monitors 54 individual Nintex components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Nintex goes down?

Yes. Create a free account and subscribe to Nintex: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Nintex to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Nintex problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Nintex?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Nintex plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Nintex with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services