Vendor reports: major outageResolved · vendor status “resolved”Official status API

Primosign - Connection to primosign.quovadisglobal.com are failing with 500 error

Reported by DigiCert · Identity & Security · source last read 2 min ago

Vendor start
Nov 11, 2025, 08:50 UTC
Vendor's clock
Resolved
Nov 11, 2025, 21:57 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
13 h 7 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • DigiCert reports major outage: "Primosign - Connection to primosign.quovadisglobal.com are failing with 500 error".[E1, E2]
  • The vendor marked it resolved at 2025-11-11 21:57 UTC.[E3, E7]

Affected products and regions

  • Components: DSS-Engine Production.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-11-11 21:57 UTC · summary s1, evidence a60771442884d471

Evidence (7)
  1. E1DigiCert reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Primosign - Connection to primosign.quovadisglobal.com are failing with 500 error". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-11-11 08:50 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: DSS-Engine Production. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-11-11 21:57 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: DSS-Engine Production

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

DigiCert is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 11, 2025, 08:50 UTCVendor-reported startVendor time
  2. Nov 11, 2025, 21:57 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.