Live  /  SafeNet Trusted Access  /  Incident

SafeNet Trusted Access: Classic - Admin Console Access and SAML/OIDC Authentication Incident

SafeNet Trusted Access · safenetid.comMajor incidentResolved2026-10-15 03:56 UTC
Public — what happened

Summary

SafeNet Trusted Access reported a major incident on its Classic service beginning at 02:17 UTC on 2026-10-15, saying some customers were having trouble with the admin console, the API and SAML/OIDC sign-in. According to the company, this could stop administrators from managing items such as users, tokens, policies and application settings, and could keep end users from logging in to business apps connected to the service. The company did not describe a cause, but said a fix was put in place at 03:35 UTC, and the incident was marked resolved at 03:56.

Affected

Authentication Services, Admin Consoles, End User Services

As listed on SafeNet Trusted Access’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 43, 2026, our weekly internet health report.

The full archive is on the SafeNet Trusted Access status & history page.

Related: SafeNet Trusted Access status & history. SquidGrid is not affiliated with SafeNet Trusted Access.