Universign incident

Identified Major outage

Major Resolved View vendor source →

Universign experienced a major incident on March 18, 2024 affecting Transaction Service and Timestamp Service and 1 more component, lasting 8h 5m. The incident has been resolved; the full update timeline is below.

Started
Mar 18, 2024, 10:21 AM UTC
Resolved
Mar 18, 2024, 06:26 PM UTC
Duration
8h 5m
Detected by Pingoru
Mar 18, 2024, 10:21 AM UTC

Affected components

Transaction ServiceTimestamp ServiceSeal ServiceWeb ApplicationRegistration ServicePlatform Availability

Update timeline

  1. identified Mar 18, 2024, 10:21 AM UTC

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

  2. identified Mar 18, 2024, 10:47 AM UTC

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

  3. identified Mar 18, 2024, 11:09 AM UTC

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

  4. identified Mar 18, 2024, 11:39 AM UTC

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

  5. identified Mar 18, 2024, 12:12 PM UTC

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

  6. monitoring Mar 18, 2024, 12:45 PM UTC

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

  7. monitoring Mar 18, 2024, 01:19 PM UTC

    We are continuing to monitor for any further issues.

  8. identified Mar 18, 2024, 02:06 PM UTC

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

  9. identified Mar 18, 2024, 02:27 PM UTC

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

  10. identified Mar 18, 2024, 02:50 PM UTC

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

  11. identified Mar 18, 2024, 03:24 PM UTC

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

  12. identified Mar 18, 2024, 03:44 PM UTC

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

  13. identified Mar 18, 2024, 03:45 PM UTC

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

  14. identified Mar 18, 2024, 04:10 PM UTC

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

  15. identified Mar 18, 2024, 04:13 PM UTC

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

  16. identified Mar 18, 2024, 04:37 PM UTC

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

  17. identified Mar 18, 2024, 05:00 PM UTC

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

  18. monitoring Mar 18, 2024, 05:02 PM UTC

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

  19. monitoring Mar 18, 2024, 06:23 PM UTC

    We are continuing to monitor for any further issues.

  20. resolved Mar 18, 2024, 06:26 PM UTC

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