Universign 장애 기록

1. 2026년 7월 30일 AM 8:02 UTCinvestigating

   주 메뉴 부패 웹 est actuellement indisponible. L’ensemble de nos équipes est mobilisé afin d’assurer un retour à la normale dans les plus brefs délais. 관련 상품 L'équipe 지원

2. 2026년 7월 30일 AM 8:10 UTCidentified

   스낵 바 La 원인 été identifiée et des investigations complémentaires sont en cours. Nous mettons tout en œuvre 부 rétablir les 서비스 dans les plus brefs délais. Cordialement,

3. 2026년 7월 30일 AM 8:11 UTCmonitoring

   스낵 바 été déployé et nous surveillons actuellement les résultats가 아닌 정확한 경우. Cordialement, L'équipe 지원

4. 2026년 7월 30일 AM 8:19 UTCresolved

   주 메뉴 노우스 vous informons que l'incident est à présent résolu. Nous vous prions de nous 변명기 부 les désagréments 때때로 à votre disposition 부 toute 정보 complémentaire. Cordialement, L'équipe 지원

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 10일 PM 5:13 UTCinvestigating

   Bonjour, Nous rencontrons actuellement des perturbations sur notre plateforme affectant l'envoi des SMS. La non-réception des SMS est constatée de manière aléatoire pour certains utilisateurs. Nos équipes sont pleinement mobilisées afin d'identifier l'origine de l'incident et de résoudre le blocage dans les meilleurs délais. Nous vous remercions pour votre compréhension et vous tiendrons informés de l'évolution de la situation. Cordialement, L'équipe Support

2. 2026년 7월 10일 PM 5:14 UTCidentified

   Bonjour Nous souhaitons vous informer que la source du problème a été identifiée. Nous mettons tout en œuvre pour rétablir le service dans les plus brefs délais. Cordialement, L'équipe Support

3. 2026년 7월 10일 PM 5:15 UTCmonitoring

   Bonjour Un correctif a été déployé et nous surveillons actuellement les résultats. Cordialement, L'équipe Support

4. 2026년 7월 10일 PM 5:15 UTCresolved

   Bonjour, Nous vous informons que l’incident est à présent résolu. Nous vous prions de nous excuser pour les désagréments occasionnés et restons à votre disposition pour toute information complémentaire. Cordialement, L’équipe Support

1. 2026년 5월 11일 AM 6:03 UTCinvestigating

   Bonjour, Nous vous informons que notre plateforme connaît actuellement des perturbations. Nous ne manquerons pas de vous tenir informés dès que la situation sera entièrement résolue. Cordialement, L'équipe Support

2. 2026년 5월 11일 AM 6:03 UTCidentified

   Bonjour La cause a été identifiée et des investigations complémentaires sont en cours. Nous mettons tout en œuvre pour rétablir les services dans les plus brefs délais. Cordialement, L'équipe Support

3. 2026년 5월 11일 AM 6:04 UTCmonitoring

   Bonjour Un correctif a été déployé et nous surveillons actuellement les résultats. Cordialement, L'équipe Support

4. 2026년 5월 11일 AM 6:05 UTCresolved

   Bonjour, Nous vous informons que l’incident est à présent résolu. Nous vous prions de nous excuser pour les désagréments occasionnés et restons à votre disposition pour toute information complémentaire. Cordialement, L’équipe Support

1. 2026년 4월 13일 PM 7:18 UTCinvestigating

   Bonjour Des perturbations affectent actuellement la plateforme. Nos équipes travaillent à rétablir le service au plus vite. Merci pour votre compréhension. Cordialement, L'équipe Support

2. 2026년 4월 13일 PM 7:18 UTCidentified

   Bonjour La cause a été identifiée et des investigations complémentaires sont en cours. Nous mettons tout en œuvre pour rétablir les services dans les plus brefs délais. Cordialement, L'équipe Support

3. 2026년 4월 13일 PM 7:19 UTCmonitoring

   Bonjour Un correctif a été déployé et nous surveillons actuellement les résultats. Cordialement, L'équipe Support

4. 2026년 4월 13일 PM 7:19 UTCresolved

   Bonjour, Nous vous informons que l’incident est à présent résolu. Nous vous prions de nous excuser pour les désagréments occasionnés et restons à votre disposition pour toute information complémentaire. Cordialement, L’équipe Support

1. 2026년 4월 7일 AM 8:07 UTCidentified

   Bonjour, Nous souhaitons vous informer que la source du problème a été identifiée. Nos équipes sont mobilisées afin de rétablir la situation dans les meilleurs délais. Merci pour votre compréhension. L'équipe Support

2. 2026년 4월 7일 AM 9:52 UTCidentified

   Bonjour Les actions de rétablissement du service se poursuivent et nos équipes demeurent entièrement mobilisées afin de restaurer la disponibilité dans les meilleurs délais. Cordialement L'équipe Support

3. 2026년 4월 7일 AM 10:36 UTCidentified

   Bonjour, L’incident est toujours en cours et nos équipes poursuivent leurs investigations pour en accélérer la résolution. Nous restons mobilisés et vous remercions pour votre patience. Merci pour votre compréhension. L'équipe Support

4. 2026년 4월 7일 PM 12:36 UTCidentified

   Bonjour L’incident est toujours en cours. Nous mettons tout en œuvre pour rétablir les services dans les plus brefs délais Cordialement, L'équipe Support

5. 2026년 4월 7일 PM 1:57 UTCidentified

   Bonjour Des perturbations affectent actuellement la plateforme. Nos équipes travaillent à rétablir le service au plus vite. Merci pour votre compréhension. Cordialement, L'équipe Support

6. 2026년 4월 7일 PM 4:30 UTCidentified

   Bonjour, Nous poursuivons nos efforts afin de rétablir l’ensemble des services de notre plateforme dans les meilleurs délais. Nous vous tiendrons informés de toute évolution à ce sujet. Cordialement, L’équipe Support

7. 2026년 4월 7일 PM 6:37 UTCidentified

   Bonjour, Les travaux de rétablissement du service se poursuivent. L’ensemble de nos équipes est mobilisé afin d’assurer un retour à la normale dans les plus brefs délais. Cordialement, L'équipe Support

8. 2026년 4월 7일 PM 8:17 UTCmonitoring

   Bonjour Un correctif a été déployé et nous surveillons actuellement les résultats. Cordialement, L'équipe Support

9. 2026년 4월 7일 PM 8:19 UTCresolved

   Bonjour, Nous vous informons que l’incident est à présent résolu. Nous vous prions de nous excuser pour les désagréments occasionnés et restons à votre disposition pour toute information complémentaire. Cordialement, L’équipe Support

1. 2026년 3월 13일 PM 3:39 UTCinvestigating

   Bonjour, Nous rencontrons actuellement des perturbations sur notre plateforme (création des certificats). Nos équipes sont mobilisées afin d'identifier l'origine et de rétablir la situation dans les meilleurs délais. Merci pour votre compréhension. Cordialement, L'équipe Support

2. 2026년 3월 13일 PM 3:41 UTCinvestigating

   Bonjour La cause a été identifiée et des investigations complémentaires sont en cours. Nous mettons tout en œuvre pour rétablir les services dans les plus brefs délais Cordialement, L'équipe Support

3. 2026년 3월 13일 PM 4:57 UTCidentified

   Bonjour La cause a été identifiée et des investigations complémentaires sont en cours. Nous mettons tout en œuvre pour rétablir les services dans les plus brefs délais Cordialement, L'équipe Support

4. 2026년 3월 13일 PM 5:43 UTCidentified

   Bonjour Les actions de rétablissement du service se poursuivent et nos équipes demeurent entièrement mobilisées afin de restaurer la disponibilité dans les meilleurs délais. Cordialement L'équipe Support

5. 2026년 3월 13일 PM 6:01 UTCmonitoring

   Bonjour Un correctif a été mis en place et nous surveillons actuellement les résultats. Cordialement, L'équipe Support

6. 2026년 3월 13일 PM 6:17 UTCresolved

   Bonjour, L’incident est désormais résolu. Nous vous prions de nous excuser pour la gêne occasionnée. Cordialement, L’équipe Support

1. 2026년 1월 29일 AM 8:59 UTCinvestigating

   We are facing some issues. The creation of new certificates is not possible due to a technical issues.

2. 2026년 1월 29일 AM 9:01 UTCidentified

   The problem is identified and we are working on a fix right now.

3. 2026년 1월 29일 AM 9:04 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 1월 29일 AM 9:06 UTCresolved

   This incident has been resolved. We deeply apologize for the inconvenience.

1. 2025년 11월 18일 PM 12:00 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now. Cloudflare is experiencing an internal service degradation.

2. 2025년 11월 18일 PM 12:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 11월 18일 PM 12:12 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 11월 18일 PM 2:03 UTCresolved

   This incident has been resolved. We deeply apologize for the inconvenience.

1. 2025년 9월 29일 AM 10:08 UTCinvestigating

   We are currently experiencing difficulties on our platform. More information will be made available as it is conveyed to us.

2. 2025년 9월 29일 AM 10:23 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 9월 29일 AM 10:32 UTCresolved

   This incident has been resolved. We deeply apologize for the inconvenience.

1. 2025년 9월 25일 PM 2:15 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

2. 2025년 9월 25일 PM 2:16 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 9월 25일 PM 2:16 UTCresolved

   This incident has been resolved. We are preparing a global report about this incident. We deeply apologize for the inconvenience.

1. 2025년 9월 15일 PM 4:05 UTCinvestigating

   We are currently experiencing difficulties on our platform. More information will be made available as it is conveyed to us.

2. 2025년 9월 15일 PM 4:05 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

3. 2025년 9월 15일 PM 4:06 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2025년 9월 15일 PM 4:06 UTCresolved

   This incident has been resolved. We deeply apologize for the inconvenience.

1. 2025년 9월 1일 AM 9:43 UTCinvestigating

   We are currently experiencing difficulties on our platform.

2. 2025년 9월 1일 AM 9:43 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 9월 1일 AM 9:44 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

4. 2025년 9월 1일 AM 9:45 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2025년 9월 1일 AM 9:45 UTCresolved

   This incident has been resolved. We deeply apologize for the inconvenience.

1. 2025년 5월 6일 PM 3:15 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 5월 6일 PM 3:16 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 5월 6일 PM 3:22 UTCresolved

   This incident has been resolved.

1. 2024년 12월 18일 PM 3:12 UTCinvestigating

   We are currently experiencing difficulties on our platform. More information will be made available as it is conveyed to us.

2. 2024년 12월 18일 PM 3:42 UTCidentified

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

3. 2024년 12월 18일 PM 4:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 12월 19일 AM 7:48 UTCresolved

   This incident has been resolved.

5. 2024년 12월 19일 PM 12:05 UTCpostmortem

   **Incident Report – December 18, 2024** On December 18, 2024, between 3:20 PM and 4:45 PM \(CET\), we experienced an issue affecting our transaction service with some periods of unavailability. Other services on the platform, such as the Seal and Timestamp APIs, were not impacted. Our system relies on several storage servers \(SAN\) to store customer data and ensure redundancy across physical devices. One of these servers, dedicated to temporarily storing transaction-related documents \(from creation to archival 30 days later\), encountered an internal issue and automatically switched to read-only mode as a protective measure. After multiple unsuccessful attempts to resolve the issue with this server, we decided to redirect transaction document storage to another server. This operation triggered a data transfer from the affected server to the new one. Unfortunately, this process extended the duration of the incident, as it was essential to ensure that signers could still access transactions created before the incident. We sincerely apologize for any inconvenience this may have caused and thank you for your understanding. We remain committed to providing you with the best possible service experience. If you have any questions, please do not hesitate to contact our support team. ‌ **Rapport d'incident – 18 décembre 2024** Le 18 décembre 2024, entre 15h20 et 16h45 \(CET\), un incident a impacté notre service de transaction avec des périodes d'indisponibilité. Les autres services de la plateforme, tels que les APIs de cachet électronique et d’horodatage, n’ont pas été affectés. Notre système repose sur plusieurs serveurs de stockage \(SAN\) pour conserver les données de nos clients et garantir leur redondance sur différents dispositifs physiques. L’un de ces serveurs, dédié au stockage temporaire des documents de transaction \(de leur création à leur archivage 30 jours plus tard\), a rencontré un problème interne et s'est automatiquement mis en mode lecture seule par mesure de sécurité. Après plusieurs tentatives infructueuses pour résoudre le problème sur ce serveur, nous avons décidé de rediriger le stockage des documents de transaction vers un autre serveur. Cette opération a déclenché un transfert des données entre les deux serveurs. Malheureusement, ce processus a prolongé la durée de l’incident, car il était nécessaire pour garantir l’accès aux transactions créées avant l’incident. Nous tenons à nous excuser pour les désagréments causés et vous remercions pour votre compréhension. Nous restons mobilisés et engagés pour vous fournir la meilleure expérience client possible. Si vous avez des questions, n’hésitez pas à contacter notre équipe de support.

1. 2024년 4월 16일 AM 10:17 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

2. 2024년 4월 16일 AM 10:45 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2024년 4월 16일 AM 11:46 UTCresolved

   This incident has been resolved. We are preparing a global report about this incident. We deeply apologize for the inconvenience.

4. 2024년 4월 16일 PM 2:31 UTCpostmortem

   We observed a degradation/interruption of our services along with a new type of use of the service coming from a newly registered customer. To avoid further issues, we have disabled said client's access as well as deactivated the ability to register for the service from our website. We are currently analyzing to understand how this type of access creates an overload on our platform. Measures will be taken soon to avoid such impacts on our services.

1. 2024년 3월 26일 AM 9:31 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

2. 2024년 3월 26일 AM 11:12 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2024년 3월 26일 AM 11:12 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 3월 26일 AM 11:13 UTCresolved

   This incident has been resolved. We are preparing a global report about this incident. We deeply apologize for the inconvenience.

1. 2024년 3월 21일 PM 1:11 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

2. 2024년 3월 21일 PM 1:12 UTCidentified

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

3. 2024년 3월 21일 PM 1:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 3월 21일 PM 1:33 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2024년 3월 21일 PM 3:17 UTCresolved

   This incident has been resolved. We are preparing a global report about this incident. We deeply apologize for the inconvenience.

1. 2024년 3월 20일 AM 8:07 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

2. 2024년 3월 20일 PM 5:45 UTCidentified

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

3. 2024년 3월 20일 PM 6:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 3월 21일 AM 8:08 UTCresolved

   This incident has been resolved. We deeply apologize for the inconvenience.

1. 2024년 3월 18일 AM 10:21 UTCidentified

   We are facing a minor outage. The problem is identified and we are working on a fix right now.

2. 2024년 3월 18일 PM 2:06 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

3. 2024년 3월 18일 PM 5:00 UTCidentified

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

4. 2024년 3월 18일 PM 5:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2024년 3월 18일 PM 6:23 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2024년 3월 18일 PM 6:26 UTCresolved

   This incident has been resolved. We are preparing a global report about this incident. We deeply apologize for the inconvenience.

1. 2024년 3월 15일 AM 10:53 UTCidentified

   We are facing a minor outage. The problem is identified and we are working on a fix right now.

2. 2024년 3월 15일 AM 10:55 UTCinvestigating

   We are currently experiencing difficulties on our platform. More information will be made available as it is conveyed to us.

3. 2024년 3월 15일 AM 11:34 UTCinvestigating

   We are continuing to investigate this issue.

4. 2024년 3월 15일 PM 12:12 UTCidentified

   We are facing a major outage. The problem is identified and we are working on a fix right now.

5. 2024년 3월 15일 PM 5:14 UTCidentified

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

6. 2024년 3월 15일 PM 5:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

7. 2024년 3월 15일 PM 6:18 UTCresolved

   This incident has been resolved. We are preparing a global report about this incident. We deeply apologize for the inconvenience.