Universign incident

March 2024: Universign major outage on Transaction Service

Critical Resolved View vendor source →

Universign experienced a critical incident on March 15, 2024 affecting Transaction Service and Timestamp Service and 1 more component, lasting 10h 19m. The incident has been resolved; the full update timeline is below.

Started
Mar 15, 2024, 07:58 AM UTC
Resolved
Mar 15, 2024, 06:18 PM UTC
Duration
10h 19m
Detected by Pingoru
Mar 15, 2024, 07:58 AM UTC

Affected components

Transaction ServiceTimestamp ServiceSeal ServiceWeb ApplicationRegistration Service

Update timeline

  1. investigating Mar 15, 2024, 08:36 AM UTC

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

  2. identified Mar 15, 2024, 08:53 AM UTC

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

  3. monitoring Mar 15, 2024, 09:03 AM UTC

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

  4. identified Mar 15, 2024, 10:53 AM UTC

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

  5. investigating Mar 15, 2024, 10:55 AM UTC

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

  6. investigating Mar 15, 2024, 11:22 AM UTC

    We are continuing to investigate this issue.

  7. investigating Mar 15, 2024, 11:34 AM UTC

    We are continuing to investigate this issue.

  8. identified Mar 15, 2024, 12:12 PM UTC

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

  9. identified Mar 15, 2024, 12:31 PM UTC

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

  10. identified Mar 15, 2024, 12:58 PM UTC

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

  11. identified Mar 15, 2024, 01:44 PM UTC

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

  12. identified Mar 15, 2024, 02:22 PM UTC

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

  13. identified Mar 15, 2024, 02:55 PM UTC

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

  14. identified Mar 15, 2024, 03:17 PM UTC

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

  15. identified Mar 15, 2024, 03:44 PM UTC

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

  16. identified Mar 15, 2024, 04:16 PM UTC

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

  17. identified Mar 15, 2024, 04:41 PM UTC

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

  18. identified Mar 15, 2024, 05:14 PM UTC

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

  19. monitoring Mar 15, 2024, 05:18 PM UTC

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

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

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