Incident: e-signing(VismaSign) impacted due to third-party provider issue

Incident Report for Sympa

Postmortem

Between 21 February at 12:00 EET and 24 March at 13:40 EET, users using VismaSign experienced issues with the e-signing functionality due to a disruption on the VismaSign side.

According to VismaSign and their partner Twoday, the issue was caused by an expired certificate, which has since been renewed. Logs indicate that traffic returned to normal after the fix, and new documents have been created successfully since.

The service is now fully operational. Please let us know if you continue to experience any issues.

Posted Mar 25, 2025 - 17:42 EET

Resolved

The issue has been resolved and VismaSign should now be fully functional.

Posted Mar 25, 2025 - 15:38 EET

Monitoring

We've solved the issue together with the 3rd party and necessary changes have been deployed to production systems yesterday afternoon.

We're still monitoring the situation.

Posted Mar 25, 2025 - 13:10 EET

Update

The issue is identified to affect only VismaSign and the problem is on the Visma side. We have notified the provider and we are monitoring for updates on their side.

Posted Mar 24, 2025 - 17:15 EET

Update

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

Posted Mar 24, 2025 - 17:14 EET

Identified

We are currently experiencing issues with the e-signing functionality, which is being impacted by a disruption with our third-party provider. Our team is actively monitoring the situation and working with the provider to restore full service as quickly as possible.

We will continue to provide updates as we receive more information. Thank you for your patience.

Posted Mar 24, 2025 - 12:44 EET

This incident affected: Integrations and Esign.