Nintex status history
Current state: major outage — “Service Disruption” per https://status.nintex.com (Status.io), checked 2026-09-16 12:28 UTC.
3incidents, last 30 days
3incidents, last 90 days
3incidents on record
Status.io only exposes incidents that are open right now, so this history starts on 2026-09-04, the day we first watched Nintex. It fills in from here.
Incidents on record (3)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 10:44 UTC | DocGen for Salesforce failures due to Salesforce's API outage | investigating | — | open |
| 2026-09-10 15:36 UTC | User management page not loading users | investigating | — | 3 d 20 h (approx.) |
| 2026-09-04 19:01 UTC | Nintex K2 Cloud service maintenance | maintenance | maintenance | 6 d 17 h (approx.) |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Nintex with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"nintex"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}