DocSpera incident

Service Disruption — Authentication Errors (AWS Outage)

Minor Resolved View vendor source →

DocSpera experienced a minor incident on September 3, 2026, lasting 1h 51m. The incident has been resolved; the full update timeline is below.

Started
Sep 03, 2026, 10:23 PM UTC
Resolved
Sep 04, 2026, 12:15 AM UTC
Duration
1h 51m
Detected by Pingoru
Sep 03, 2026, 10:23 PM UTC

Update timeline

  1. investigating Sep 03, 2026, 10:23 PM UTC

    We are currently experiencing intermittent authentication errors on DocSpera due to an AWS service disruption affecting the us-west-2 (Oregon) region. AWS has reported increased API error rates for STS (Security Token Service) and SAML sign-in beginning at 2:12 PM PDT. Impact: Users may be unable to log in, or may experience errors during active sessions that require re-authentication. Core clinical data and scheduling records are not affected. We are monitoring AWS's status closely and will post updates as new information becomes available. There is currently no workaround on our end, as this is an upstream provider issue. We apologize for the disruption and appreciate your patience.

  2. investigating Sep 04, 2026, 12:14 AM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 04, 2026, 12:15 AM UTC

    The AWS service disruption affecting authentication on DocSpera has been fully resolved. Login and identity federation are now operating normally. Root cause: AWS identified an issue in an STS subsystem responsible for communicating with external identity providers, affecting the AssumeRoleWithSAML and AssumeRoleWithWebIdentity APIs in us-west-2. This impacted SAML-based sign-in and session authentication on DocSpera. Impact: Minor API service disruption.