Portnox Outage History

Portnox is up right now

Pingoru has recorded 1 incident for Portnox: 1 in the last 12 months and 0 in the last 90 days.

Source: status.portnox.com

1incidents recorded
1last 12 months
0last 90 days
18 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Portnox in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202610 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 513 (0%)

Incidents, newest first

Major June 23, 2026 Service Disruption Notice: Local RADIUS Service Issues Under Investigation 18m America, Europe, Authentication Services, Authentication Services (RADIUS)

Started Jun 23, 2026, 02:53 AM UTC· resolved Jun 23, 2026, 03:11 AM UTC

  1. investigating Jun 23, 2026, 02:53 AM UTC

    We have received several reports from customers experiencing issues with the Local RADIUS service. Our DevOps and Engineering teams are actively investigating the issue to identify the root cause and implement a resolution. At this time, there is no known service disruption affecting Portnox Cloud RADIUS services. Customers using Cloud RADIUS services should continue to operate normally. Recommended Action for Affected Customers: Customers who may be impacted by this issue are advised to temporarily shut down their Local RADIUS services and fail over to Portnox Cloud RADIUS services until the issue has been resolved. We will continue to provide updates as more information becomes available. We appreciate your patience while our teams work to restore full service functionality.

  2. resolved Jun 23, 2026, 03:11 AM UTC

    Update 10:09 PM CDT — Local RADIUS Service Issue Resolved The issue affecting Local RADIUS instances has been resolved. Our DevOps and Engineering teams have restored service functionality and are actively monitoring the environment to ensure continued stability. We appreciate your patience and cooperation while our teams worked to resolve this issue.

Read the full incident report →