Universign incident

Identified major outage

Critical Resolved View vendor source →

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

Started
Mar 20, 2024, 07:12 AM UTC
Resolved
Mar 21, 2024, 08:08 AM UTC
Duration
1d
Detected by Pingoru
Mar 20, 2024, 07:12 AM UTC

Affected components

Transaction ServiceTimestamp ServiceSeal ServiceWeb ApplicationRegistration Service

Update timeline

  1. identified Mar 19, 2024, 08:26 AM UTC

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

  2. identified Mar 19, 2024, 08:50 AM UTC

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

  3. identified Mar 19, 2024, 09:10 AM UTC

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

  4. identified Mar 19, 2024, 09:30 AM UTC

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

  5. identified Mar 19, 2024, 09:50 AM UTC

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

  6. identified Mar 19, 2024, 10:11 AM UTC

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

  7. identified Mar 19, 2024, 10:31 AM UTC

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

  8. identified Mar 19, 2024, 10:51 AM UTC

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

  9. identified Mar 19, 2024, 11:02 AM UTC

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

  10. identified Mar 19, 2024, 11:03 AM UTC

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

  11. identified Mar 19, 2024, 11:45 AM UTC

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

  12. identified Mar 19, 2024, 12:06 PM UTC

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

  13. identified Mar 19, 2024, 12:40 PM UTC

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

  14. identified Mar 19, 2024, 01:04 PM UTC

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

  15. identified Mar 19, 2024, 01:46 PM UTC

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

  16. identified Mar 19, 2024, 02:08 PM UTC

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

  17. identified Mar 19, 2024, 02:35 PM UTC

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

  18. identified Mar 19, 2024, 02:57 PM UTC

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

  19. identified Mar 19, 2024, 03:23 PM UTC

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

  20. identified Mar 19, 2024, 04:12 PM UTC

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

  21. identified Mar 19, 2024, 04:40 PM UTC

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

  22. monitoring Mar 19, 2024, 05:25 PM UTC

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

  23. identified Mar 20, 2024, 08:07 AM UTC

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

  24. identified Mar 20, 2024, 09:15 AM UTC

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

  25. identified Mar 20, 2024, 09:43 AM UTC

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

  26. identified Mar 20, 2024, 10:04 AM UTC

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

  27. identified Mar 20, 2024, 10:25 AM UTC

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

  28. identified Mar 20, 2024, 10:43 AM UTC

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

  29. identified Mar 20, 2024, 11:03 AM UTC

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

  30. identified Mar 20, 2024, 11:22 AM UTC

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

  31. identified Mar 20, 2024, 11:48 AM UTC

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

  32. identified Mar 20, 2024, 12:09 PM UTC

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

  33. identified Mar 20, 2024, 12:32 PM UTC

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

  34. identified Mar 20, 2024, 12:54 PM UTC

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

  35. identified Mar 20, 2024, 01:27 PM UTC

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

  36. identified Mar 20, 2024, 02:02 PM UTC

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

  37. identified Mar 20, 2024, 02:32 PM UTC

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

  38. identified Mar 20, 2024, 03:18 PM UTC

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

  39. identified Mar 20, 2024, 03:48 PM UTC

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

  40. identified Mar 20, 2024, 04:18 PM UTC

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

  41. identified Mar 20, 2024, 04:57 PM UTC

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

  42. identified Mar 20, 2024, 05:21 PM UTC

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

  43. identified Mar 20, 2024, 05:45 PM UTC

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

  44. monitoring Mar 20, 2024, 06:02 PM UTC

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

  45. resolved Mar 21, 2024, 08:08 AM UTC

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