SecureAuth Service Status & Alerts

SecureAuth Corporation publishes the most up-to-date information on Services status as well as important Security Alerts and Patching updates. Sign up today to be notified of any Security alerts or Service interruptions.

If you're experiencing a real-time operational issue that is not described below, please submit a Support Ticket: Submit Support Ticket

Sign Up

Only Business Domain Emails Accepted
Current Service Status:

SMS Services 
Telephony Service
Push Notification Services 
Certificate Signing Services



Security Alerts and Required Operating System Patching

Operating System Patch Management: SecureAuth recommends and supports the installation of your preferred Operating System patch management system. Please review Security Alerts and Required Operating System Patching section of the SecureAuth Service Status and Alerts page for information related to Operating System patches. Apply patches 48-hours after Microsoft’s release to give our QA and Engineering team adequate time to perform testing. Apply all applicable Microsoft high priority updates/patches and reboot the Appliance after all updates.

April 15, 2015 - Microsoft has released an update to address a critical vulnerability in the HTTP protocol stack, HTTP.sys. SecureAuth recommends all customer's apply the security update MS15-034 (KB3042553) to their SecureAuth Appliances within their infrastructure as soon as possible. Security experts, including the SANS Institute, have warned of publicly available denial-of-service exploits targeting Microsoft IIS web servers are in the wild. The SANS internet Storm Center has raised the threat level of this vulnerability to "Yellow".

More information on this specific vulnerability are given below.

SANS Institute:
"MS15-034: HTTP.sys (IIS) DoS And Possible Remote Code Execution. PATCH NOW"
"Windows HTTP Protocol Stack Flaw is Being Actively Exploited (April 16, 2015)"
MS15-034: HTTP.sys Remote Code Execution Vulnerability - April 15, 2015
Microsoft Security Bulletin MS15-034 - Critical

A remote code execution vulnerability exists in the HTTP protocol stack (HTTP.sys) that is caused when HTTP.sys improperly parses specially crafted HTTP requests. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of the System account.
To exploit this vulnerability, an attacker would have to send a specially crafted HTTP request to the affected system.

Affected Appliance OS Versions:
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
Suggested Action:
Apply MS15-034 Update as soon as possible. This update addresses the vulnerability by modifying how the Windows HTTP stack handles requests.

MS15-041: Vulnerability in .NET Framework Could Allow Information Disclosure - April 15, 2015
Microsoft Security Bulletin MS15-041 - Important

The vulnerability could allow information disclosure if an attacker sends a specially crafted web request to an affected server that has custom error messages disabled. An attacker who successfully exploited the vulnerability would be able to view parts of a web configuration file, which could expose sensitive information.

Affected .NET Versions:
  • Microsoft .NET Framework 1.1 Service Pack 1
  • Microsoft .NET Framework 2.0 Service Pack 2
  • Microsoft .NET Framework 3.5
  • Microsoft .NET Framework 3.5.1
  • Microsoft .NET Framework 4
  • Microsoft .NET Framework 4.5
  • Microsoft .NET Framework 4.5.1
  • Microsoft .NET Framework 4.5.2 on affected releases of Microsoft Windows
Affected Appliance OS Versions:
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
Suggested Action:
Apply MS15-041 Update as part of you standard patching process. By default, SecureAuth IdP enables a custom error message and encrypts sensitive sections of the Web configuration file. This update addresses the vulnerability by removing file content details from the error messages that were facilitating the information disclosure.

MS14-066: Microsoft Schannel Remote Code Execution Vulnerability – November 12, 2014
Microsoft has released a security update in response to a privately reported vulnerability (MS14-066) in the Microsoft Secure Channel (Schannel) security package in Windows. The vulnerability could allow remote attackers to execute arbitrary code against Windows Servers, via crafted packets. This vulnerability has a CVSS base score of 10 (High), and the security update from Microsoft is rated as critical for all supported releases of Windows. This vulnerability affects Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1. Further information on the vulnerability, as well as a complete list of all impacted versions of Windows can be found in in the following Microsoft Security Bulletin:   Also see the NIST NVD assessment details of this vulnerability here:

SecureAuth has completed functionality testing of the MS14-066 security update against SecureAuth IdP 8.0 running on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 based appliances. At this time, SecureAuth did not encounter any issues with the application of the MS14-066 security update. SecureAuth is in the process of completing functionality testing on earlier supported versions of SecureAuth IdP.

Due to the severity of this vulnerability, SecureAuth is recommending that all customers test the Microsoft MS14-066 security update, and upon successful testing, apply this to all SecureAuth IdP appliances as soon as possible.

Poodle Vulnerability – October 16, 2014
A security vulnerability affecting SSL 3.0, known as “POODLE”, was recently disclosed to the public. This is an industry-wide vulnerability that affects the SSL 3.0 protocol itself. SecureAuth IdP appliances are shipped with SSL 3.0 enabled to ensure backwards compatibility with legacy customer product, therefore are vulnerable to the POODLE exploit. At this time, the only way to mitigate the SSL 3.0 issue is to disable it on the SecureAuth IdP appliance. Please note that if there are legacy devices on your network that only support SSL 3.0, disabling it on the appliance will prevent those devices from communicating. It’s advised that you perform an audit of your networks critical services before disabling SSL 3.0.
Below please find instructions for disabling SSL 3.0 on a SecureAuth IdP Appliance. This process will require a reboot and should be performed during an authorized maintenance window. “Disabling SSL 3.0 on a SecureAuth IdP Appliance” - .  If you require assistance with the documented process, please don’t hesitate to call support. We will be happy to assist you with disabling SSL 3.0.

Report a problem

Click this link to open a Support ticket

Status and Alert History

Below are historical Service status and Security alerts.  If you have questions, please contact SecureAuth support.

Services History

General Services

September 2, 2013 - Expiration of legacy Intermediate Certificate Authority Certificate –A legacy intermediate Issuing CA certificate is expiring at approximately 10pm on 9/2/2013 PDT.  Access to VPN resources using the respective VPN thick client and native personal certificates may be impacted if certain environmental conditions exist.  Please follow this link for more information if you are experiencing VPN client access issues.

April, 27, 2013 - At 5:43AM PDT SecureAuth Operations was alerted to a low disk space issue on one of the primary Web Servers. After an investigation to the cause of the disk condition it was determined the index service had created a catalog file on the Web Server’s primary OS drive. Due to this low disk space condition the Web Services could not publish some content. The Index service has been reconfigured and the disk space alert levels will be changed to send notifications earlier to avoid any additional problems.  All systems have been tested operational.

SecureAuth SMS Services

June 1, 2015 - SecureAuth was notified by our telephony provider of intermittent delivery issues with SMS (TXT) messages in the United States. This issue affected all US carriers and had the potential to impact 30% of all regional SMS traffic. The issue started around 7:55 AM PDT and was resolved at 8:10 AM PDT. There should be no further impact to customers.

If you have any questions regarding this incident, please feel free to contact SecureAuth Support at +1-866- 859-1526.

April 15, 2015 - The SMS outage which started on 2015-04-15 at 9:30 PM PDT was resolved on 2015-04-16 9:25 AM PDT.

The root cause investigation for the outage had determined the initial assessment that the application of a security update by a SMS route sub-provider causing SMS delivery failures was correct. The security update only affected a portion of our SMS provider's customer base who use long code SMS services. Troubleshooting this issue was made more difficult, which resulted in a longer outage, due to the sub-provider not rejecting new SMS requests as it normally would in this situation therefore the fail-over to a functional provider did not occur.

To resolve the issue SecureAuth's service application was reconfigured to use Short Code SMS. redundancy of the short code services is much greater now due to the majority of providers today support short SMS codes.

Additional testing and escalation procedures are being implemented by SecureAuth's SMS services provider to better ensure outage related cases are properly routed and escalated as appropriate and in a time sensitive manner.

Note: SecureAuth used long code SMS services because carrier regulations did not allow Long Codes to be used for SMS broadcasting therefore were considered more reliable. Recently, the industry has moved towards the majority use of short codes vs long codes because concerns regarding SMS broadcasting (spamming) have reduced and regulation have changed controlling short code usage.

April 3rd, 2015 - At approximately 11:35 AM PST SecureAuth was notified by T-Mobile of a service outage in their SMS platform affecting customers located in the United States. This may cause delays in delivery of OTP SMS messages. The issue was resolved at 12:22 PM PST.

March 5th, 2015 - At approximately 7:15 PM PST the SecureAuth cloud services experienced an outage impacting SMS, Push, Telephony and Certificate Signing services.
Service requests could not be processed because public DNS resolution failed to resolve the services host name. SecureAuth engineering was notified of name resolution failures at 7:15pm PST by our monitoring service. At that time SecureAuth contacted the service provider hosting the DNS Zone for the domain requesting an investigation and resolution of the issue.
While the service provider worked to determine the root cause of the name resolution failure, SecureAuth engineering migrated the DNS Start of Authority to a new DNS provider in order to minimize downtime and impact to customers.
Propagation of the SOA change was completed and Services were completely restored by 9:00pm PST. 
Action Taken:
As a result of this outage, we have taken action to improve DNS reliability and prevent this from recurring by moving the SOA to a commercial DNS provider with multiple Name Servers to assure continued up time and future improved availability.

February 19, 2015 - At approximately 1:00 PM PST on Thursday, February 19th, the SecureAuth cloud services experienced an outage impacting SMS and Telephony services.

Service requests could not be processed because the production database was unavailable due to the failure of the MS SQL Server fail-over cluster environment. SecureAuth engineering was notified of the loss of connection to the SQLAgent and SQLServer services at 1.29pm PST. At that time a review of the MS SQL cluster environment determined we could manually migrate services to re-enable SQL Services. The SQL Service application processes were immediately migrated and they were confirmed operational again at 1.39pm PST.

Detail of Issue: 
There are two SQL Server nodes in an active/passive cluster managed by Microsoft Cluster Services (MSCS). A MSCS service identified a node connection failure and attempted to move services to the passive node, however, the intermittent loss of virtual network connectivity between the cluster nodes caused the fail-over process itself to fail.  The intermittent loss of network connectivity has been attributed to a network adapter driver ,which caused an issue with the Microsoft Failover Cluster Virtual Adapter. It is this adapter which is responsible for determining the nodeís network configuration and connectivity with other nodes in the cluster.
Actions Taken:
As a result of this outage, we have taken several actions to improve the reliability of the cluster and prevent this recurring. The actions taken are as follows:
 1) The virtual network adapter firmware and driver was updated as recommended by the vendor on the MS SQL server nodes. No new cluster fail-over error events have occurred since this update was completed.
2) The MS Cluster disk timeout has been increased from the default of 60 seconds to the Microsoft recommended setting of 120 seconds.
3) We have identified events being logged on the systems indicating non-fatal loss of network connectivity that we are monitoring in addition to monitoring the main MS SQL Server services.
4) The alerting services provider is being configured to send alerts via email and text message for MS SQL Server cluster fail-over related service error events to avoid delayed notifications going forward.

October 16, 2014 - Between the hours of 12:45 AM PDT to 7:30AM PDT, some of our customers reported that some of their users were unable to receive their OTPs via the SMS option. After an internal investigation revealed that our systems were running as expected, a support ticket was opened with our Service Provider (Telesign). Their evaluation also concluded that all services were functioning normally. Telesign then inquired upstream about specific non-deliveries to Carrier Operators, from which it was determined that Sprint and Google Voice, among other smaller US operators, were having network issues. T-Mobile users were also affected, which can be attributed to the fact that carriers often times share towers. With that being said, although the cause for the service interruption had nothing to do with SecureAuth or Telesign uptime, we certainly understand the impact of the disruption and are working with Telesign to streamline the information gathering process so that we may provide more details regarding carrier issues.

September 12, 2013 – SecureAuth SMS Services will be updated starting at 11:00pm PDT on September 12, 2013 and completing at 1:00am PDT September 13, 2013.  There may be some delays in SMS delivery during short periods during this window, but we do not anticipate any major delays or outages. UPDATE: The configuration changes were completed and SMS Services are tested and fully functional.

September 3, 2014 - SecureAuth SMS Services experienced slowness on Wednesday, September 3 at approximately 7:50 AM PDT and again Friday September 5 @ 6:30AM PDT. Customers may have experienced excessively long wait times and/or possibly an error message when using the SMS one-time password option. The issue has been resolved and all systems are functioning normally. Root Cause: Large numbers of simultaneous SMS requests and subsequent SMS provider acknowledgement updates to the SMS table caused excessive CPU and Disk IO load on the SQL server cluster servicing the Hosted services database. It has been determined that the root cause of this condition was a con

June 20th 2013 - Intermittent SMS delivery issues in the US across multiple mobile carriers - SecureAuth Customers may have experienced SMS delivery delays or outages starting Thursday, June 20th at approximately 6::00am Pacific Daylight Time. The cause of these issues were due to problems with the SMS network routes which connect Telesign, our SMS service provider, to all the mobile operators/carriers. Telesign updated the SMS routes which were causing these delays/failures to resolve the issue at 8:32am PDT and continues to monitor and work with the mobile carriers to ensure that no additional routes require updates.


SecureAuth Telephony Services 

SecureAuth Push Notification Services




SecureAuth Certificate Services

March 23, 2016 At 10:30AM PDT - We are currently experiencing intermittent issues with SHA1 certificate delivery. If you are using our SHA1 legacy certificate service for certificate enrollment, you are affected. We are currently working on resolving the issue and will send out a notification as soon as services have been restored. If you have any questions regarding the matter please feel free to contact SecureAuth Support with any questions.

January 18th, 2014 - SecureAuth Services experienced a temporary outage which some customers experienced certificate signing issues. This issue was resolved and all systems are functioning as expected. Root Cause: The outage was determined to have been caused by a local firewall change blocking TCP Port 80 on one of the SecureAuth certificate authority distribution point web servers. A new Anti-virus application was installed earlier in the week which made the change. Resolution: The local firewall was modified on the affected certificate authority distribution point web server to allow the appropriate communications. Going forward: Future functionality testing plans will include additional verification of connectivity testing to avoid this and similar service and/or communication issues from occurring.

SecureAuth Security and Patching Bulletins

Microsoft Security Advisory 2868725 - On November 12th, 2014 Microsoft released Security Advisory 2868725 to addresses known weaknesses in the RC4 cipher. This update supports the removal of RC4 as an available cipher on affected systems through registry settings. Update for Disabling RC4 - Discussion: The Microsoft Security Advisory 2868725 disables all RC4 ciphers on systems to which it is applied. If this patch is applied to a SecureAuth server which has a realm configured for LDAPS, communications may become interrupted. At this time we can confirm an interruption of service if the LDAP server is Active Directory running on Windows Server 2003 or earlier. Regardless of configuration we recommend performing regression testing in your development environment before applying this patch to your production SecureAuth systems. Workaround - If you have already installed the patch on your SecureAuth appliance and are experiencing interruptions in LDAPS communications you can restore connectivity by uninstalling the Security Advisory 2868725 patch.