Live / SafeNet Trusted Access / Incident
SafeNet Trusted Access: Classic - Authentication Services Incident
SafeNet Trusted Access · safenetid.comMinor incidentResolved2026-10-09 00:58 UTC
Public — what happened
Summary
SafeNet Trusted Access reported a minor problem with its Classic authentication services beginning at 00:29 UTC on 2026-10-09, after its own monitoring flagged the issue. The company said customers might have trouble signing in through RADIUS, which can block VPN and network access, as well as SAML/OIDC business applications and the admin consoles used to manage users, tokens and policies. It described the trouble as intermittent, noting that repeated attempts usually worked. No cause has been given, and the Thales response team was still investigating with the incident unresolved.
Affected
Authentication Services, Admin Consoles, End User Services, Push Delivery, Management
Timeline
- Started — 2026-10-09 00:29 UTC
- Investigating — 2026-10-09 00:29 UTC (2 updates)
- Resolved — 2026-10-09 00:58 UTC · 30 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach SafeNet Trusted Access against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for SafeNet Trusted Access: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the SafeNet Trusted Access report →
More from SafeNet Trusted Access
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.