Last 90 days uptime
Service uptime (90 days)
Per-component uptime from the Status.io API.
Incident timeline
About this page
This page tracks 90-day uptime for all 27 Nintex platform services, sourced directly from the status.nintex.com Status.io API. Data is fetched daily and committed to this repository automatically.
Unlike Atom-feed-based trackers, Status.io exposes a per-component 90-day uptime endpoint that provides structured daily status and incident data — no historical replay or feed parsing required. Incident intervals are used to compute minute-level downtime, deduplicating cross-component overlaps for the platform-wide uptime figure.
Nerd notes: platform uptime is computed by merging all component incident
intervals (minute-level, deduplicating overlaps). Per-component uptime is derived the same
way from each component's own incident windows. Only minor and
major status codes (300, 400, 500) count as downtime; maintenance (200) does not.