Resolved after 31 minutes, affecting Admin Portal, on June 11, 2025.
## **Description** We experienced a temporary issue in our Azure Kubernetes Service \(AKS\) environment that affected the availability of key services due to a sudden increase in traffic. ## **Root Cause** A sudden and significant spike in access to EU Xink service led to increased demand on our infrastructure. As a result, some components in our Azure Kubernetes Service \(AKS\) cluster were unable to start due to insufficient available resources at the time. This caused delays in deploying services. ## **Impact** * Xink Portal inaccessible during incident * Signatures inaccessible during incident ## **Resolution** * **Immediate Action:** Increased the number of nodes in the AKS cluster to provide additional compute resources, allowing pending components to be scheduled and services to recover. * **Permanent Fix:** Adjusted auto-scaling thresholds and resource allocation policies to better handle sudden spikes in traffic without resource exhaustion. * **Deployment:** Applied configuration changes and resource scaling updates during the incident and validated them in production to ensure stability. * **Monitoring:** Post-resolution monitoring confirmed that all services are operating normally and resource levels remain healthy under load.
Affected components
Update timeline
- investigating Jun 11, 2025, 08:18 AM UTC
We are currently investigating this issue.
- resolved Jun 11, 2025, 08:50 AM UTC
We already applied fixes. Please allow up to 30 minutes for the service to get to normal operation.
- postmortem Jun 11, 2025, 11:37 AM UTC
## **Description** We experienced a temporary issue in our Azure Kubernetes Service \(AKS\) environment that affected the availability of key services due to a sudden increase in traffic. ## **Root Cause** A sudden and significant spike in access to EU Xink service led to increased demand on our infrastructure. As a result, some components in our Azure Kubernetes Service \(AKS\) cluster were unable to start due to insufficient available resources at the time. This caused delays in deploying services. ## **Impact** * Xink Portal inaccessible during incident * Signatures inaccessible during incident ## **Resolution** * **Immediate Action:** Increased the number of nodes in the AKS cluster to provide additional compute resources, allowing pending components to be scheduled and services to recover. * **Permanent Fix:** Adjusted auto-scaling thresholds and resource allocation policies to better handle sudden spikes in traffic without resource exhaustion. * **Deployment:** Applied configuration changes and resource scaling updates during the incident and validated them in production to ensure stability. * **Monitoring:** Post-resolution monitoring confirmed that all services are operating normally and resource levels remain healthy under load.
Your product runs on more than Xink
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services