ProNavigator Outage History
ProNavigator is up right nowPingoru has recorded 19 incidents for ProNavigator: 2 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 1 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 0 | 0 of 509 (0%) |
Incidents, newest first
Notice September 8, 2026 ProNavigator Authentication Service Degradation 1h 2m
Started Sep 08, 2026, 01:10 PM UTC· resolved Sep 08, 2026, 02:12 PM UTC
- identified Sep 08, 2026, 01:10 PM UTC
We have identified the cause of the issue affecting ProNavigator logins. The problem is related to an error during a recent authentication protocol upgrade. We are actively applying mitigation steps to restore system access and will share another update shortly.
- identified Sep 08, 2026, 01:30 PM UTC
A fix for the authentication protocol error has been successfully deployed. We are currently monitoring system performance
- monitoring Sep 08, 2026, 01:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 08, 2026, 02:12 PM UTC
Login issues are fully resolved. All ProNavigator services are now operating normally.
Notice June 9, 2026 ProNavigator Knowledge Management Web Application Interruption 1h 2m
Started Jun 09, 2026, 08:45 PM UTC· resolved Jun 09, 2026, 09:47 PM UTC
- resolved Jun 10, 2026, 08:14 PM UTC
On June 9th, 2026, at approximately 4:45 PM EDT ProNavigator Knowledge Management experienced a service interruption that affected a number of clients. The incident prevented users from accessing the platform if they attempted a fresh load of the web application. Note that active users prior to the incident would not have experienced an interruption unless the application was reloaded. Service was fully restored at 5:47 pm EDT following a configuration rollback.
Minor October 20, 2025 Amazon DNS issues 10h 22m Library
Started Oct 20, 2025, 02:58 PM UTC· resolved Oct 21, 2025, 01:20 AM UTC
- monitoring Oct 20, 2025, 02:58 PM UTC
We're aware that a small number of users are currently experiencing issues with documents not loading. This appears to be tied to DNS issues following the AWS issues. While ProNavigator's systems remain fully operational, Amazon has reported ongoing DNS resolution issues in some external services. These can impact document access for certain users. In most cases, clearing your browser cache and DNS cache has resolved the issue. If problems persist, please contact our support team and we'll be happy to help. We're actively monitoring the situation and will share any updates as needed.
- resolved Oct 21, 2025, 01:20 AM UTC
Amazon is now reporting their services are restored. If any problems persist for individual users, it is recommended they clear their browser and DNS cache.
Major June 6, 2025 Autoprovisioned SSO User Login 10m Login
Started Jun 06, 2025, 07:33 PM UTC· resolved Jun 06, 2025, 07:43 PM UTC
- investigating Jun 06, 2025, 07:33 PM UTC
Autoprovisioned SSO users are unable to login with error: {"message": "Endpoint request timed out"}
- monitoring Jun 06, 2025, 07:38 PM UTC
A fix has been applied and we are monitoring.
- resolved Jun 06, 2025, 07:43 PM UTC
Affected users are now able to login.
Major May 27, 2025 Spinning on login for some users 3h 47m Login
Started May 27, 2025, 02:02 PM UTC· resolved May 27, 2025, 05:49 PM UTC
- identified May 27, 2025, 02:02 PM UTC
Login is experiencing knock on effects of an outage in a 3rd party service. This prevents some users from access the platform depending on their ISP. ProNavigator team is implementing a workaround to restore access to affected users ASAP.
- identified May 27, 2025, 03:35 PM UTC
A fix has been deployed, and any impacted users can now log in. The ProNavigator team will continue monitoring over the next 24–48 hours to ensure there are no outstanding issues.
- monitoring May 27, 2025, 03:36 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 27, 2025, 05:49 PM UTC
This incident has been resolved.