Due to region-wide issues with Azure SQL databases, signing request processing as well as configuration interface was unavailable.
Excerpt from Azure’s Preliminary Post Incident Review:
]]>Multiple Azure services in West Europe
- Start time: 2026-10-27T15:25:39.007Z
- Resolve time: 2026-10-27T16:31:00.000Z
Between approximately 14:38 UTC and 17:30 UTC on 27 October 2026, multiple Azure services in the West Europe region may have experienced increased latency, connectivity issues, failed requests, or difficulties performing management operations. The incident originated from a power event affecting infrastructure within one of the datacenter facilities supporting Availability Zone 1 (AZ01) in West Europe. The power interruption caused a number of racks and the network, compute, and storage infrastructure hosted within them to lose power or connectivity.
Because this infrastructure supports multiple Azure services, the initial datacenter impact subsequently resulted in service-specific impact across portions of the region.
SaaS application components were be re-deployed due to major changes. All interruptions were within the range of regular software updates.
]]>Signing did not work after a deployment with certificates that
Temporary HSM signing outage due to a misconfiguration after deployment.
Due to an upgrade in our networking infrastructure, expect temporary problems when using or managing HSM keys and certificates. Software keys and customers using dedicated DPoD HSM instances are not affected.
No significant downtimes during the maintenance operation.
]]>Announced: Due to an upgrade in our networking infrastructure, expect temporary problems when using or managing HSM keys and certificates. Software keys and customers using dedicated DPoD HSM instances are not affected.
Actual downtimes:
Unfortunately the update had to be rolled back and will be rescheduled for a later date.
]]>GitHub APIs experienced degraded performance which may have affected SignPath’s GitHub integration.
]]>Some file-based signing requests ran into unexpected “processing errors”.
Planned migration within our login/identity provider infrastructure (Okta): upgrade to a new “identity engine”.
]]>Temporary HSM network performance degradation led to automatic service restart escalation.
Temporary HSM network performance degradation led to automatic service restart escalation.
Using the SignPath GitHub Actions submit-signing-request action did not work. (A globally scoped ID value has passed the max-int boundary at GitHub.com.)
]]>Planned maintenance for the gateway that handles incoming network traffic.
For customers using Thales DPoD Cloud HSM, completion of signing requests was delayed until after the outage and synchronous hash-based signing failed.
]]>Planned maintenance for SignPath HSM cluster’s infrastructure.
Planned maintenance for SignPath’s HSM cluster.
Planned maintenance for SignPath’s HSM cluster.
For customers using Thales DPoD Cloud HSM, completion of signing requests was delayed until after the outage and synchronous hash-based signing failed.
]]>For customers using Thales DPoD Cloud HSM, completion of signing requests was delayed until after the outage and synchronous hash-based signing failed.
]]>One node dealing with certificates on the software key store experienced network problems for signing operations. Signing requests with HSM-based keys were not affected.
]]>For customers using Thales DPoD Cloud HSM, completion of signing requests was delayed until after the outage.
]]>For customers using Thales DPoD Cloud HSM, completion of signing requests was delayed until after the outage. (The origin of the connectivity problems could not be established, additional network probes added.)
]]>Some signing requests were not processed after an application update.
]]>Failed signing requests for some customers using dedicated Thales DPoD Cloud HSM instances (DNS issue during DPoD maintenance).
]]>For all customers using their own Thales DPoD Cloud HSMs hosted in the EU, signing operations may briefly be interrupted due to maintenance operations by Thales.
]]>Problems in the database backend caused temporarily outdated lists and reports.
]]>Importing private keys from PFX files into the HSM key store did not work (fixed in release 1.152).
]]>Planned maintenance for SignPath’s HSM cluster.
The domain signpath.io was not resolved by our domain registrar’s name servers. Problem detection was delayed as many systems including our monitoring were using cached DNS entries, and support email transmission was affected by the same problem.
]]>Performance issues due to a regression caused by a dependency. We noticed performance degradation in queue processing during the following periods:
As an initial reaction to 1 and 2, we allocated additional computing resources. Once the root cause was identified, we reverted the system to an old version of the component that caused the issue and deployed it as a hotfix.
]]>We are reconfiguring the network connection to our HSM cluster for better availability. Operations using HSM keys will fail during this period. Software keys and customers using dedicated DPoD HSM instances are not affected.
]]>A configuration error caused a processing queue buildup from 9:15. The error was resolved by 11:00. By 11:30, the queue was processed completely and operations back to normal. Hash-based signing requests were not affected.
]]>Due to multi-region network problems in Microsoft Azure (Tracking ID VSG1-B90), a small percentage of signing requests was failing. In most situations, this was mitigated by automated retries.
]]>One node experienced low-level infrastructure problems for signing operations. The issue could not be identified at runtime, so affected signing requests were not retried and failed immediately.
]]>Due to problems with the timestamp authority, several signing requests had to be rescheduled and completed late.
]]>Due to outages of Azure SQL in the West Europe region, the web application and REST API were temporarily unavailable.
]]>Due to problems with the timestamp authority, several signing requests had to be rescheduled and completed late.
]]>Due to problems with the timestamp authority, several signing requests had to be rescheduled and completed late.
]]>Our outbound proxy was temporarily out of service. This resulted in delays for Webhook notifications and signing requests that retrieve artifacts via URL.
]]>The Azure Application Gateway was temporarily unavailable several times, but self-healed immediately each time
]]>Due to network configuration changes, HSM-based signing will experience problems. All signing requests will continue processing when network connectivity is restored.
]]>Due to network configuration changes, HSM-based signing will experience intermittent problems. All signing requests will continue processing when network connectivity is restored.
]]>We are changing our authentication provider to Okta. This is the first of two migration steps.
]]>Our payment provider will do some maintenance, resulting in possible intermittent availability impact to platform services summing 1 hour. Service to existing customers of SignPath will not be affected.
]]>Due to a reconfiguration of our internet provider, the processing of HSM-based signing requests and creating/deleting certificates may be temporarily unavailable.
]]>Due to a reconfiguration of our internet provider, the processing of HSM-based signing requests and creating/deleting certificates may be temporarily unavailable.
]]>Due to an upgrade in our networking infrastructure, problems performing operations involving the Hardware Security Module (HSM), such as signing operations or creating new certificates might occur.
]]>During the deployment of a new version of SignPath, infrastructure problems arose. The release was rolled back, but some downtime could not be avoided. One of the servers did not start correctly in the process, causing the API to be unavailable for certain customers.
]]>Due to an upgrade in our networking infrastructure, problems performing operations involving the Hardware Security Module (HSM), such as signing operations or creating new certificates might occur.
]]>Due to an upgrade in our networking infrastructure, problems performing operations involving the Hardware Security Module (HSM), such as signing operations or creating new certificates might occur.
]]>Due to a Storage incident in the Azure datacenter in the West Europe regions, our services had several outages.
]]>