Skip to main content
Nintex logo

Is Nintex Down?

No — Nintex is up

Reachable from all 8 checked regions

Average response time: 217ms

Last checked · checks run every 6 hours

Official status page: https://status.nintex.com

Nintex uptime

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

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

30-day history

27-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: 100.00% uptime, 16 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 31 checks
Sep 3: 100.00% uptime, 28 checks
Sep 4: 100.00% uptime, 32 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 22 checks
Sep 7: 100.00% uptime, 7 checks
Sep 8: 100.00% uptime, 30 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, 30 checks
Sep 13: 100.00% uptime, 31 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 56 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 38 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 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.

iad
452ms
DNS 153ms TCP 8ms TLS 13ms TTFB 416ms
jnb
346ms
DNS 312ms TCP 0ms TLS 7ms TTFB 339ms
lax
201ms
DNS 104ms TCP 1ms TLS 6ms TTFB 187ms
lhr
149ms
DNS 122ms TCP 1ms TLS 5ms TTFB 140ms
nrt
262ms
DNS 220ms TCP 1ms TLS 7ms TTFB 254ms
ord
75ms
DNS 49ms TCP 1ms TLS 6ms TTFB 67ms
sin
190ms
DNS 156ms TCP 1ms TLS 6ms TTFB 176ms
sjc
64ms
DNS 25ms TCP 1ms TLS 6ms TTFB 46ms

What Nintex does

Nintex automates business processes for around 7,000 companies, mainly in manufacturing, financial services, government and healthcare. The platform covers workflow approvals and routing, document generation through DocGen, robotic process automation, and process mapping in Process Manager. Finance, HR and IT teams build approval chains on it, so an outage stops work moving between people rather than taking a website offline.

What an outage looks like

Submitted forms and approvals stop advancing, and requests sit in the queue without reaching the next approver. DocGen jobs return no document or fail inside Salesforce. Nintex List Forms embedded in SharePoint Online pages will not load or will not submit. Scheduled RPA bots do not run. Because every product is reported per region, a failure in one region leaves the same workflow working for colleagues elsewhere.

What to do about it

Open status.nintex.com and find your own region under the affected product: Automation Cloud, DocGen, Process Manager, K2 Cloud and RPA are each broken out across the United States, Europe, Australia, Canada, the United Kingdom, Singapore and other regions. Resubmitting an approval usually creates a duplicate rather than fixing anything. Nintex Automation K2 installed on your own servers runs independently of the cloud services.

Is it down for everyone, or just you?

If this page says Nintex 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

Nintex outage FAQ

Is Nintex down for everyone or just my region?
Often just one region. The Nintex status page reports each product separately for the United States, Europe, Australia, Canada, the United Kingdom, Singapore and US Government, among others. A workflow that fails for your team can keep running normally for colleagues on a different regional tenant, so the headline banner is less useful than the row matching your own region.
Does a Nintex outage affect self-hosted K2?
No. Nintex Automation K2 is the self-hosted option, run on your own servers by organizations that need data sovereignty or on-premises deployment, and it does not depend on the Nintex cloud services. The status page does list Nintex K2 Cloud and K2 Trust separately, which are the hosted versions; those are the rows that matter if you use K2 as a cloud service.
Why did my DocGen document never generate?
DocGen is reported as its own component, separately from Nintex Automation Cloud, and separately again for Salesforce and for the FedRAMP environment. A DocGen incident leaves the rest of your workflow working while document generation fails, which is why a request can move through its approvals and then stop at the point where the paperwork should have appeared.
Does a Nintex outage affect SharePoint or Salesforce?
Not the other way around: SharePoint Online and Salesforce keep running, but the Nintex pieces embedded in them stop. Nintex List Forms for SharePoint Online and Nintex DocGen for Salesforce are separate components on the status page, so a SharePoint page can load perfectly while the Nintex form on it fails, which makes the problem look like a SharePoint fault.
Does the status page cover Process Manager?
Yes, and in more detail than most. Process Manager appears as Production, Freetrial/Demo, free trial site provisioning and the Reporting API, each with its own regional rows. If process maps load but reports do not, the Reporting API row is the one to read. Nintex Customer Central and Partner Central are also listed separately from the automation products.

How we measure this

  • We request Nintex'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 Nintex 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 Nintex 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