RSA ID Plus Status Page

Oct 2, 2026 · resolved Oct 2

After monitoring the fix, SaaS Operations has determined that the incident affecting RSA ID Plus has been resolved. We will post a root cause analysis as soon as it is available.

Sep 14, 2026 · resolved Sep 14

**Initial Root Cause Analysis** **Summary** On September 14, 2026, between approximately 06:20 UTC and 07:20 UTC, a subset of customers hosted in the RSA ID Plus EU2 production environment experienced authentication service degradation. During the incident, authentication requests were intermittently unable to complete successfully. Across the affected authentication traffic, RSA estimates that approximately 15–20% of authentication attempts succeeded during the period of degradation. The level of impact varied by customer and authentication flow. **What Happened** Beginning at approximately 06:20 UTC, authentication processing latency and failure rates increased within the EU2 environment. The degradation affected portions of the request-processing path used by the authentication service and resulted in elevated error rates for a subset of customers in the EMEA region. RSA engineering teams investigated the affected services and supporting infrastructure. Service performance improved as processing conditions stabilized, and authentication success rates returned to expected levels by approximately 07:20 UTC. **Root Cause** RSA has not yet identified a definitive root cause for this incident. Our investigation remains active and includes a review of application telemetry, authentication traffic patterns, request-processing behavior, and supporting infrastructure within the EU2 environment. Initial analysis shows that authentication demand, request retries, processing latency, and resource utilization increased during the incident window. RSA is working to establish the relationship among these conditions, determine the sequence of events, and identify which conditions initiated or amplified the degradation. These findings remain preliminary and should not be interpreted as a final determination of root cause. **Resolution** Service performance recovered as the affected processing environment stabilized. RSA engineering teams confirmed that authentication latency, error rates, and service throughput had returned to expected levels and continued monitoring the EU2 environment following recovery. RSA did not initiate regional failover during the incident because the environment remained partially operational and did not meet the criteria for an automated regional transition. RSA maintains regional failover capabilities to support service continuity during regional service events. In this case, preliminary analysis indicated that the conditions contributing to the degradation would likely have followed authentication traffic to the recovery region. Based on those conditions, RSA did not expect a regional transition to resolve the degradation and determined that it could reproduce the same behavior in the recovery environment. RSA has not identified any customer configuration changes required in response to this incident. **Actions and Ongoing Investigation** RSA is continuing a detailed investigation and is taking steps to reduce the likelihood and potential impact of similar events. This work includes: * Analyzing authentication traffic, retry patterns, and service dependencies to establish the complete sequence of events. * Reviewing request-handling and capacity controls to prevent elevated activity associated with a single customer or connection path from affecting other customers in the environment. * Evaluating retry and timeout behavior to reduce amplification during periods of service congestion. * Reviewing load distribution across application components and investigating the uneven error distribution observed during the incident. * Enhancing service telemetry and alerting for processing latency, resource saturation, abnormal retry behavior, and dependencies supporting customer-connected components. * Evaluating additional capacity and resiliency measures for authentication processing within the EU2 environment. RSA will provide an updated RCA within 10 business days of the incident. If the investigation remains open at that time, RSA will provide the findings available to date, the status of remaining investigative work, and any additional corrective actions identified.

Jun 26, 2026 · resolved Jun 26

Customers hosted in the RSA EU West production environment experienced intermittent authentication failures and service degradation. The issue was resolved, and service has returned to normal operation. RSA continues to investigate the underlying cause in collaboration with our cloud service provider.

Jun 15, 2026 · resolved Jun 15

Customers hosted in the RSA EU West production environment experienced intermittent authentication failures and service degradation. The issue was resolved, and service has returned to normal operation. RSA continues to investigate the underlying cause in collaboration with our cloud service provider.

Jun 4, 2026 · resolved Jun 4

**Summary** On June 4, 2026, between approximately 04:48:49 UTC and 05:00:18 UTC, customers hosted in the RSA EU West production environment experienced intermittent authentication failures and service degradation resulting from a cloud-provider networking event. **What Happened** During the incident window, RSA services experienced connectivity disruptions to underlying cloud infrastructure dependencies within our cloud provider environment. These connectivity issues impacted communication between application components and supporting platform services required for authentication processing. As a result, authentication requests were intermittently unable to complete successfully, resulting in customer-facing service degradation. **Timeline of Events** Application telemetry indicates the event consisted of multiple periods of degradation and recovery as the underlying cloud-provider networking infrastructure stabilized and recovery operations were processing. While customer impact was observed between approximately 04:49 UTC and 05:00 UTC, the severity of the event fluctuated during that period rather than remaining constant throughout. **Root Cause** RSA completed an investigation in collaboration with our cloud provider. The incident was caused by a planned cloud provider platform maintenance activity that resulted in unexpected instability within shared networking infrastructure servicing cloud platform dependencies in the EU West region. The networking instability affected connectivity between RSA application services and cloud platform services required for authentication processing, including caching and storage dependencies used by the authentication platform. As part of the investigation, RSA confirmed that the affected systems were distributed across multiple independent infrastructure groups, as required by the architecture of ID Plus. This distribution is a foundational design principle of the EU West environment and is intended to isolate routine maintenance activities and localized infrastructure failures from causing broader service impact. However, the cloud provider determined that this event involved shared networking infrastructure servicing multiple infrastructure groups simultaneously. As a result, systems that would normally operate independently experienced connectivity degradation at the same time, reducing the effectiveness of the within-region resiliency mechanisms designed to protect against localized infrastructure events. The cloud provider further determined that the maintenance activity did not proceed as expected and resulted in networking instability that exceeded the duration and recovery characteristics normally associated with routine platform maintenance activities. RSA services are designed to tolerate the brief transient interruptions that can occur during normal cloud platform maintenance operations, and the behavior observed during this incident was not representative of the brief interruptions typically expected during standard maintenance events. **Resolution** RSA engineering teams responded to the incident, validated service recovery, and engaged the cloud provider to perform a detailed review of the underlying infrastructure event. During the incident, RSA monitoring and automated service recovery mechanisms detected the degradation and initiated standard recovery actions designed to maintain service availability and recover application health. These actions included automated platform health monitoring and workload recovery processes operating within the affected environment. Service stability was restored as connectivity within the underlying cloud provider infrastructure recovered and networking services stabilized. Once connectivity was re-established, application services returned to normal operation and customer authentication processing resumed successfully.

Is RSA ID Plus down right now?

No — RSA ID Plus is up. All systems operational as of Oct 12, 4:54 AM UTC.

What is RSA ID Plus's current status?

RSA ID Plus: All Systems Operational. Alert24 checks RSA ID Plus's status page continuously and can notify you the moment it changes.

How do I get alerted when RSA ID Plus goes down?

Alert24 monitors RSA ID Plus and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.