Summary:
On February 12, 2026, our authentication system experienced a temporary service disruption due to an unexpected failure of the Kubernetes master node.
Impact:
During this period, the administrative front-end interface was unavailable, preventing administrators from accessing the management console.
It is important to note that corporate services were not affected. Specifically:
Email tracking (opened emails, clicked links, submissions, etc.) continued to function normally.
Campaign delivery and tracking mechanisms remained fully operational.
No data loss occurred.
The issue was isolated to the authentication layer serving the admin front-end.
Root Cause:
The disruption was caused by a crash of the Kubernetes master node, which temporarily impacted the authentication service responsible for admin access.
Resolution:
The Kubernetes master node was restored and stabilized. Network and cluster services were verified, and full functionality of the authentication system was successfully restored.
Preventive Actions:
Additional monitoring and stabilization measures have been implemented to reduce the likelihood of similar disruptions in the future.
If you require any further details, please feel free to contact us.
No components marked as affected
Investigating
Summary:
On February 12, 2026, our authentication system experienced a temporary service disruption due to an unexpected failure of the Kubernetes master node.
Impact:
During this period, the administrative front-end interface was unavailable, preventing administrators from accessing the management console.
It is important to note that corporate services were not affected. Specifically:
Email tracking (opened emails, clicked links, submissions, etc.) continued to function normally.
Campaign delivery and tracking mechanisms remained fully operational.
No data loss occurred.
The issue was isolated to the authentication layer serving the admin front-end.
Root Cause:
The disruption was caused by a crash of the Kubernetes master node, which temporarily impacted the authentication service responsible for admin access.
Resolution:
The Kubernetes master node was restored and stabilized. Network and cluster services were verified, and full functionality of the authentication system was successfully restored.
Preventive Actions:
Additional monitoring and stabilization measures have been implemented to reduce the likelihood of similar disruptions in the future.
If you require any further details, please feel free to contact us.
