DigiCert experienced a major incident on September 4, 2026 affecting DigiCert ONE Console (Global) and digicert.com Login (Global) and 1 more component, lasting 3h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 04, 2026, 10:03 AM UTC
We are currently experiencing a technical problem with our DigiCert Support Email System and are working to resolve the issue as quickly as possible. We are tracking this issue under Case# 05116620 While we work to restore access to our DigiCert Support Email System , you can contact us through: Telephone: Call us Chat: Chat with us Email: Message us We apologize for any inconvenience this may cause you. DigiCert Support We apologize for any inconvenience this may cause you. DigiCert Support デジサート ウェブサイトセキュリティアラート情報 – DigiCert Alert 現在、 DigiCert Support Email System はテクニカル面における問題が確認されており、復旧にむけて調査を進めています。 ケース番号 05116620 何かご不明な点、ご質問等がございましたらこちらからお願いいたします。 Telephone: Call us Chat: Chat with us Email: Message us ご不便をお掛けして申し訳ございませんが、何卒ご理解のほどよろしくお願いいたします。 デジサートウェブサイトセキュリティサポート
- investigating Sep 04, 2026, 10:30 AM UTC
We are continuing to investigate this issue.
- investigating Sep 04, 2026, 10:31 AM UTC
We are currently experiencing a technical problem with our DigiCert Support Email System and are working to resolve the issue as quickly as possible. We are tracking this issue under Case# 05116620 While we work to restore access to our DigiCert Support Email System , you can contact us through: Telephone: Call us Chat: Chat with us Email: Message us We apologize for any inconvenience this may cause you. DigiCert Support We apologize for any inconvenience this may cause you. DigiCert Support デジサート ウェブサイトセキュリティアラート情報 – DigiCert Alert 現在、 DigiCert Support Email System はテクニカル面における問題が確認されており、復旧にむけて調査を進めています。 ケース番号 05116620 何かご不明な点、ご質問等がございましたらこちらからお願いいたします。 Telephone: Call us Chat: Chat with us Email: Message us ご不便をお掛けして申し訳ございませんが、何卒ご理解のほどよろしくお願いいたします。 デジサートウェブサイトセキュリティサポート
- identified Sep 04, 2026, 11:11 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Sep 04, 2026, 01:08 PM UTC
This incident has been resolved.