Secured Signing incident

Secured signing all Regions - Azure Access Issues- DNS

Critical Resolved View vendor source →

Secured Signing experienced a critical incident on October 29, 2025 affecting Secured Signing Website US Region and Secured Signing Website AUS Region and 1 more component, lasting 5h 15m. The incident has been resolved; the full update timeline is below.

Started
Oct 29, 2025, 04:44 PM UTC
Resolved
Oct 29, 2025, 09:59 PM UTC
Duration
5h 15m
Detected by Pingoru
Oct 29, 2025, 04:44 PM UTC

Affected components

Secured Signing Website US RegionSecured Signing Website AUS RegionSecured Signing Website NZ RegionSecured Signing Website UK Region

Update timeline

  1. investigating Oct 29, 2025, 04:44 PM UTC

    Azure (Microsoft - Global Data Center provider) is experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions.

  2. investigating Oct 29, 2025, 04:46 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 29, 2025, 05:24 PM UTC

    Azure is experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. This issue affecting our service,

  4. investigating Oct 29, 2025, 06:55 PM UTC

    Azure team - We have initiated the deployment of our last known good configuration of Front Door, which is expected to complete A.S.A.P. We do not yet have an ETA for full mitigation, but we will provide another update once the deployment has completed.

  5. identified Oct 29, 2025, 07:26 PM UTC

    The issue has been identified and a fix is being implemented.

  6. identified Oct 29, 2025, 07:46 PM UTC

    Azure Notification We are actively working to recover affected nodes and anticipate full mitigation within the next four hours. Some customers may be able to log in; however, service delays are expected during this recovery period. We will provide further updates as soon as more information becomes available.

  7. identified Oct 29, 2025, 08:35 PM UTC

    We are continuing to work on a fix for this issue.

  8. identified Oct 29, 2025, 08:45 PM UTC

    We are continuing to work on a fix for this issue.

  9. monitoring Oct 29, 2025, 09:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  10. resolved Oct 29, 2025, 09:59 PM UTC

    This incident has been resolved.