Yousign Incident History

1. resolvedSep 4 · 21:06 UTC

   Resolved. The backlog is fully delivered: every email held up during the incident has now been sent, and delivery to Microsoft business mailboxes has been back to normal since Microsoft closed its incident. What happened: from around 11:30 CEST, a global Microsoft incident on inbound mail stopped our notifications from reaching business mailboxes hosted by Microsoft 365 and Exchange Online. Personal addresses such as outlook.com, hotmail.com and live.com were never affected, and no other email provider was involved. Our systems kept sending normally throughout, and the messages were queued by our provider rather than lost. Once Microsoft restored service, that queue was flushed over the following hours, which is why some notifications arrived late this afternoon and this evening. The cause and the fix were both on Microsoft's side. What we can improve is how quickly we detect a blockage at a single provider and tell you about it, and we are working on that. Thank you for your patience, and sorry for the disruption this caused to your day.

Reported by Yousign on their status page.

1. ResolvedSep 4 · 21:06 UTC

   Resolved. The backlog is fully delivered: every email held up during the incident has now been sent, and delivery to Microsoft business mailboxes has been back to normal since Microsoft closed its incident.What happened: from around 11:30 CEST, a global Microsoft incident on inbound mail stopped our notifications from reaching business mailboxes hosted by Microsoft 365 and Exchange Online. Personal addresses such as outlook.com, hotmail.com and live.com were never affected, and no other email provider was involved. Our systems kept sending normally throughout, and the messages were queued by our provider rather than lost.Once Microsoft restored service, that queue was flushed over the following hours, which is why some notifications arrived late this afternoon and this evening.The cause and the fix were both on Microsoft's side. What we can improve is how quickly we detect a blockage at a single provider and tell you about it, and we are working on that.Thank you for your patience, and sorry for the disruption this caused to your day.

Reported by Yousign on their status page.

1. resolvedSep 2 · 15:19 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. ResolvedSep 2 · 15:19 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedSep 1 · 18:08 UTC

   All Identity Verification services are now fully operational, and we have implemented additional measures to enhance service stability based on insights on our provider infrastructure. We are now closing this incident, and sincerely apologise for any inconvenience caused.

Reported by Yousign on their status page.

1. ResolvedSep 1 · 18:08 UTC

   All Identity Verification services are now fully operational, and we have implemented additional measures to enhance service stability based on insights on our provider infrastructure. We are now closing this incident, and sincerely apologise for any inconvenience caused.

Reported by Yousign on their status page.

1. resolvedAug 13 · 16:05 UTC

   As of 18:05 (CEST), this incident is resolved. All pending Advanced (AES) signatures have been processed, and the signature delay has been fully cleared. Both Advanced (AES) and Qualified (QES) signature flows are operating normally, along with all other operations on the platform. We apologise for the inconvenience caused and thank you for your patience.

Reported by Yousign on their status page.