Classic Service Zone    
Quaterly Failover Resiliance Testing
Scheduled Maintenance Report for SafeNet Trusted Access - Classic Zone
The scheduled maintenance has been completed.
Posted Jan 25, 2020 - 17:00 UTC
All services verified and running on Primary site and are performing within nominal levels. Failback confirmed as successful.

Further testing will be conducted, however, no user-impact is expected for the duration of the maintenance window.
Posted Jan 25, 2020 - 15:11 UTC
Core services have online on Primary Site.
Posted Jan 25, 2020 - 14:58 UTC
Commencing failback to Primary site.
Posted Jan 25, 2020 - 14:54 UTC
DNS Failover complete. Authentication, Monitoring and Reporting services reporting stable in DR site and serving users without issue.
Posted Jan 25, 2020 - 14:08 UTC
Beginning failover. We will update when core services are verified in DR site.
Posted Jan 25, 2020 - 14:04 UTC
DNS Failover of core services will begin within the next few minutes.

A brief disruption can be expected as core services failover.

We will provide an update as we begin.
Posted Jan 25, 2020 - 14:03 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jan 25, 2020 - 14:01 UTC
SafeNet Trusted Access Quarterly Failover Test - Classic

In our ongoing pursuit of service stability and resilience, we will be performing our quarterly Failover Test in the Classic environment on January 25th, 2020 between the hours of 14:00 UTC and 17:00 UTC
During this period, brief outages up to an expected maximum of 15 minutes will occur at the beginning and near the end of the window as we conduct the failover and failback. It is also possible for some service degradation to be experienced in terms of service responsiveness and performance as we conduct testing exercises within the window.

Complete service availability and performance will resume at the end of the window.
Updates will be provided via our Statuspage: https://status.sta.safenetid.com/

NOTE: For those who use hardcoded IP Addresses for Token Validator:
Our Disaster Recovery Plan is designed to leverage DNS to ensure a smooth and rapid failover of services. As such, during failover exercises (planned or unplanned) could cause service disruption for your users for authentication if you are to continue to use hard-coded IP addresses. It is expected that during the upcoming test, disruption times could be longer than the above-mentioned 15 minutes for those with hardcoded IP addresses.

Our next DR test is scheduled for the second quarter of 2020, so it is highly advisable to rectify this before that time, to ensure maximum service availability.

Further, as public IP addresses can be changed by the Internet Service Provider, this can increase the risk of disruption, as well as create administrative overhead for your team.

We strongly encourage the use of our FQDN: agent1.safenet-inc.com or agent2.safenet-inc.com.

If you have any questions as to how to properly add the DNS entries, we recommend using this guide as a reference:

Please note, that accessing this link does require an active Thales Support Portal account.

If you have any questions or concerns, please reach out to our Client Services team:
• United States: 800-545-6608
• International: +1-410-931-7520
We thank you for your continuous support and cooperation.

Gemalto Authentication and Access Management Cloud Services
Posted Jan 17, 2020 - 17:17 UTC
This scheduled maintenance affected: RADIUS Service (RADIUS Service (standard), RADIUS over IPsec (custom subscription)) and STA Token Management Console, STA Access Management Console, Management API (BSIDCA), SAML and OIDC Service, Authentication (Token Validator), Push OTP Service, Self-Enrollment, Self-Service and User Portal, Synchronization Service, Risk Engine, VPN UK, VPN Canada, Audit Logging, Policy Engine, Identity Provider, Auto-Provisioning Service.