Is Nintex Down?
- Nintex's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 267 ms
Right now
The verdict is the worse of these two. How we decide
Nintex's status page
status.nintex.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| US Government | Operational |
| Australasia | Operational |
FlareWarden checks
nintex.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 267 ms
- Checked
By region
- Amsterdam reachable, 202 ms
- Chicago reachable, 155 ms
- Paris reachable, 247 ms
- San Jose reachable, 254 ms
- Singapore reachable, 426 ms
- Stockholm reachable, 195 ms
- Sydney reachable, 499 ms
- Toronto reachable, 165 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 53 ms | 2 ms | 6 ms | 189 ms |
| Chicago | 131 ms | 1 ms | 3 ms | 148 ms |
| Paris | 112 ms | 2 ms | 8 ms | 236 ms |
| San Jose | 98 ms | 20 ms | 21 ms | 228 ms |
| Singapore | 179 ms | 1 ms | 4 ms | 418 ms |
| Stockholm | 52 ms | 1 ms | 4 ms | 184 ms |
| Sydney | 268 ms | 0 ms | 4 ms | 490 ms |
| Toronto | 117 ms | 1 ms | 6 ms | 155 ms |
History
Incidents Nintex reported
Since Oct 27, 10 days · from status.nintex.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Nintex website availability
Measured by FlareWarden · nintex.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 181ms
Last 30 days
73-day clean streakMeasured by FlareWarden's own checks of nintex.com from multiple regions every 6 hours. Nintex's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 73 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 17 cities across three regions to find out where it breaks.
Related services
Nintex outage FAQ
Is Nintex down for everyone or just my region?
Does a Nintex outage affect self-hosted K2?
Why did my DocGen document never generate?
Does a Nintex outage affect SharePoint or Salesforce?
Does the status page cover Process Manager?
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. 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
403or429means 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 Nintex 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 Nintex 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. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Nintex goes down
We check Nintex 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