Istoricul incidentelor Hennge One

1. 4 septembrie 2026 la 09:23 UTCinvestigating

   ---------------------------- Avem în prezent o întârziere de livrare pentru unele e-mailuri trimise la Exchange Online prin HENNGE E-mail DLP. Prin urmare, pot exista și întârzieri în primirea codurilor de autentificare pentru HENNGE Secure Download. Echipa noastră de sisteme investighează detaliile.

2. 4 septembrie 2026 la 10:37 UTCinvestigating

   Microsoft 365 (Exchange Online) Traducerea şi adaptarea: https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029 ---------------------------- [Update] În ceea ce privește întârzierile de livrare prin e-mail către Microsoft 365 (Exchange Online), Microsoft a publicat, de asemenea, informații care recunosc acest lucru ca un incident de schimb online. Pentru detalii suplimentare, vă rugăm să consultați link-ul de mai jos: Microsoft 365 Admin Center: Servicii de sănătate https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029

3. 4 septembrie 2026 la 12:36 UTCmonitoring

   Microsoft 365 (Exchange Online) Traducerea şi adaptarea: https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029 ---------------------------- În ceea ce privește întârzierea transmiterii de e-mail către Microsoft 365 (Exchange Online), am confirmat că Microsoft a luat măsuri pentru abordarea problemei. Pentru mai multe detalii, vă rugăm să consultați și următoarele informații: * Microsoft 365 admin center: Service health https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029 Vom continua să monitorizăm situaţia.

4. 7 septembrie 2026 la 00:00 UTCresolved

   Microsoft 365 (Exchange Online) Microsoft Nu. ---------------------------- Am confirmat că problema care cauzează întârzieri parțiale în livrarea de e-mail către Microsoft 365 (Exchange Online) a fost abordată de Microsoft și a fost rezolvată la 5 septembrie 2026, la 01:05 AM (JST). E-mail-urile întârziate din cauza acestui incident au fost resentimente automat, astfel încât nu este necesară nicio acțiune manuală la sfârșitul dvs. pentru a le retrimite. Ne cerem sincer scuze pentru orice neplăceri pe care le-ar fi putut cauza.

Traducere automată din actualizarea oficială a incidentului.

1. 3 septembrie 2026 la 05:20 UTCinvestigating

   - Da. Cu secure, A se vedea Decizia nr. --------------------- Am confirmat că următoarele aspecte pot apărea în prezent în HENNGE Endpoint & Managed Security: Liceele nu sunt eliberate nici după ştergerea dispozitivelor de la Portalul de Management MDR. Această problemă este cauzată de un incident în curs de desfășurare pe partea WithSecure. Pentru mai multe detalii, vă rugăm să consultați tabloul de bord de stare de mai jos: A se vedea Decizia nr. Ne cerem sincer scuze pentru orice neplăceri pe care le-ar putea cauza. Vom continua să oferim actualizări pe măsură ce situaţia progresează.

2. 4 septembrie 2026 la 01:00 UTCresolved

   Nu. Nu. --------------------- Problema a fost rezolvată și am confirmat că serviciul funcționează în mod normal. Ne cerem sincer scuze pentru orice neplăceri pe care le-ar fi putut cauza.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 08:49 UTCinvestigating

   HENNGE Email DLP Traducerea şi adaptarea: - Da. ---------------------------------- Am confirmat o problemă în care utilizatorii invitați care au primit fișiere prin intermediul HENNGE Email DLP 's Secure Download întâlnesc următoarea eroare atunci când accesează pagina de descărcare: Eroare O eroare a apărut în timpul extragerii datelor. În prezent conducem o anchetă detaliată în această problemă.

2. 16 iulie 2026 la 09:45 UTCinvestigating

   HENNGE Email DLP AWS (Servicii Web Amazon) - Da. E-mailul HENNGE DLP ---------------------------------- Iată o actualizare cu privire la această chestiune. Am confirmat că problema în care utilizatorii invitați care au primit fișiere prin intermediul HENNGE Email DLP Secure Download întâlni o eroare atunci când accesarea paginii de descărcare este cauzată de o întrerupere care afectează Amazon Web Services (AWS), pe care se bazează serviciul. În prezent, monitorizăm statutul incidentului AWS, în timp ce lucrăm la măsuri de atenuare a impactului acestuia. În acest moment, nu am confirmat niciun impact asupra e-mailurilor trimise prin intermediul HENNGE E-mail DLP. Ne cerem sincer scuze pentru neplăcerile cauzate de această problemă.

3. 16 iulie 2026 la 11:34 UTCmonitoring

   HENNGE Email DLP ---------------------------------- Iată o actualizare cu privire la această chestiune. Am confirmat că utilizatorii invitați care au primit fișiere prin intermediul HENNGE Email DLP Secure Download sunt acum în măsură să acceseze pagina de descărcare. Acest lucru se datorează faptului că AWS a implementat măsuri de atenuare a problemei care au determinat afișarea unei erori la accesarea paginii. Vom continua să monitorizăm situaţia, inclusiv pană AWS. Ne cerem sincer scuze pentru neplăcerile cauzate de această problemă.

4. 16 iulie 2026 la 12:27 UTCresolved

   HENNGE Email DLP AWS Nu. -------------------- Iată o actualizare cu privire la această chestiune. Am confirmat că AWS a anunțat rezoluția întreruperii care a cauzat problema în cazul în care utilizatorii invitați care au primit fișiere prin intermediul HENNGE Email DLP Secure Download au întâmpinat o eroare atunci când au accesat pagina de descărcare. Un raport de incident privind această problemă va fi trimis individual prin e-mail clienților cu un abonament activ la un serviciu la o dată ulterioară. Ne cerem sincer scuze pentru neplăcerile cauzate de această problemă.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 08:28 UTCinvestigating

   Traducerea şi adaptarea: ---------------------------------- Am confirmat o problemă în care este afișată următoarea eroare la accesarea HENNGE Tadrill: Eroare O eroare a apărut în timpul extragerii datelor. În prezent conducem o anchetă detaliată în această problemă.

2. 16 iulie 2026 la 09:51 UTCinvestigating

   Tadrill - Da. ---------------------------------- Iată o actualizare cu privire la această chestiune. Am confirmat că problema în care o eroare este afișată atunci când accesarea paginii Tadrill este cauzată de o întrerupere care afectează Amazon Web Services (AWS), pe care se bazează serviciul. În prezent, monitorizăm statutul incidentului AWS, în timp ce lucrăm la măsuri de atenuare a impactului acestuia. Ne cerem sincer scuze pentru neplăcerile cauzate de această problemă.

3. 16 iulie 2026 la 11:20 UTCmonitoring

   Tadril ---------------------------------- Iată o actualizare cu privire la această chestiune. În ceea ce privește problema în care a fost afișată o eroare la accesarea paginii Tadrill, echipa noastră de sistem a implementat o activitate temporară, iar pagina este acum accesibilă. Vom continua să monitorizăm situaţia, inclusiv pană AWS. Ne cerem sincer scuze pentru neplăcerile cauzate de această problemă.

4. 16 iulie 2026 la 12:28 UTCresolved

   Tadrill Nu. -------------------- Iată o actualizare cu privire la această chestiune. Am confirmat că AWS a anunțat rezoluția întreruperii care a cauzat problema în care a fost afișată o eroare la accesarea paginii Tadrill. Un raport de incident privind această problemă va fi trimis individual prin e-mail clienților cu un abonament activ la un serviciu la o dată ulterioară. Ne cerem sincer scuze pentru neplăcerile cauzate de această problemă.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 08:20 UTCinvestigating

   Traducerea şi adaptarea: - Da. ---------------------------------- Am confirmat o problemă în care este afișată următoarea eroare la accesarea Transfer Secure HENNGE: A apărut o eroare de sistem. Dacă reîncărcarea paginii nu rezolvă problema, vă rugăm să așteptați un timp și încercați din nou. În prezent conducem o anchetă detaliată în această problemă.

2. 16 iulie 2026 la 09:51 UTCinvestigating

   HENNGE Transfer Secure - Da. ---------------------------------- Iată o actualizare cu privire la această problemă. Am confirmat că problema în care este afișată o eroare atunci când accesați HENNGE Transfer Secure este cauzată de un eșec temporar în AWS (Amazon Web Services), pe care serviciul nostru îl utilizează. În prezent, verificăm starea pe partea AWS și lucrăm simultan pentru a atenua impactul. Ne cerem sincer scuze pentru orice neplăceri pe care le-ar putea cauza.

3. 16 iulie 2026 la 11:33 UTCmonitoring

   HENNGE Transfer Secure ---------------------------------- Actualizarea problemei actuale: Am confirmat că transferul securizat HENNGE este acum accesibil, deoarece AWS a aplicat măsuri de atenuare pentru a remedia erorile de acces. Vom continua să monitorizăm situaţia, inclusiv pană AWS. Ne cerem scuze pentru deranj.

4. 16 iulie 2026 la 12:27 UTCresolved

   HENNGE Transfer Secure Nu. ---------------------------------- Iată o actualizare cu privire la această problemă. În ceea ce privește problema în care a fost afișată o eroare la accesarea HENNGE Secure Transfer, am confirmat că AWS a anunțat rezoluția întreruperii subiacente care a cauzat această problemă. Un raport de incident privind această chestiune va fi trimis individual prin e-mail la o dată ulterioară clienților abonați la serviciu. Ne cerem scuze sincer pentru neplăcerile cauzate.

Traducere automată din actualizarea oficială a incidentului.

1. 12 iunie 2026 la 06:57 UTCinvestigating

   現在、HENNGE Email DLP からのメール配送の一部について Spamhaus のRBL等への誤登録により、送信先で受信拒否される事象を確認しております。 弊社システムチームにて調査を実施し、対象の RBL側へ解除の申請などをすすめております。 本事象にて受信が拒否された場合下記のようなエラーコードおよびキーワードが含まれたエラーメッセージが記載された、配信不能通知を受信することがございます。 ■エラーコード 500番代(550, 553, 554 など) （メッセージ上には「said: 550 ...」のように記載されます） ■キーワード ・Spamhaus ・Rejected ・Blocked このような配信不能通知を受け取った場合、該当のメールは宛先に配送されておりません。 お手数ではございますが時間をおいてから再度メールの再送信をお試し下さい。 ご迷惑をおかけしており恐れ入りますが、何卒よろしくお願いいたします。 ------------------------------------------------- We have confirmed an ongoing issue where certain emails routed through HENNGE Email DLP are being rejected at the destination. This is due to false-positive listings on RBLs such as Spamhaus. Our system team is actively investigating and has already initiated the delisting process with the relevant RBLs. If your message is blocked by this issue, you may receive a bounce message (NDR) containing the following error codes and keywords: ■ Error Code 500 series (Displayed in the message as "said: 550 ...") ■ Keywords - Spamhaus - Rejected - Blocked Please note that receiving this notification indicates your email was not delivered. We apologize for the trouble, but please allow some time to pass before attempting to resend your email. We apologize for the inconvenience and thank you for your cooperation.

2. 12 iunie 2026 la 09:34 UTCinvestigating

   本件につきまして続報です。 現在も事象は継続しており、弊社システムチームにて調査および、対象の RBL側へ解除の申請などをすすめております。 ご迷惑をおかけしており恐れ入りますが、何卒よろしくお願いいたします。 ------------------------------------------------- Update on this matter: The issue persists at this time. Our system team is actively investigating and continuing the delisting process with the affected RBLs. We apologize for the ongoing inconvenience and thank you for your understanding.

3. 12 iunie 2026 la 10:06 UTCmonitoring

   本件につきまして続報です。 現時点で新たな RBL誤登録やメールの受信拒否は発生しておらず解消傾向にあると考えられます。 引き続き再発等が無いか状況を監視してまいります。 ご迷惑をおかけしており恐れ入りますが、何卒よろしくお願いいたします。 ------------------------------------------------- This is an update on the ongoing issue. As of now, no further false-positive RBL listings or email blocks have been observed, and the issue appears to be resolving. We will keep monitoring the system to prevent any recurrence. We apologize for the disruption and thank you for your patience.

4. 15 iunie 2026 la 02:21 UTCresolved

   本件につきまして続報です。 その後、監視を継続してまいりましたが事象の再発は無く、解消したことを確認いたしました。 本事象の発生時間は下記の通りです。 ・2026年6月12日14時52分〜18時24分頃 ご迷惑をおかけしました事を深くお詫び申し上げます。 ------------------------------------------------- This is the final update on the issue. We have maintained our monitoring and confirmed no further recurrences. The issue is now considered completely resolved. The incident occurred during the following timeframe: - Around 14:52 to 18:24 on June 12, 2026 (JST) We deeply apologize for any disruption this may have caused.

1. 21 mai 2026 la 06:14 UTCresolved

   Email Archive におきまして、下記の時間帯に一時的に検索ができない事象が発生していた可能性があることを確認いたしました。 現在は正常に検索が行えることを確認しております。 ■事象発生期間 2026年5月19日 13時41分～14時06分頃 なお、メールのアーカイブ処理につきましては、上記時間帯においても正常に行われていたことを確認しておりますので、ご安心ください。 このたびはご迷惑をおかけしましたこと、深くお詫び申し上げます。 ---------------------------------------------------------------- We have confirmed that there may have been a temporary issue during the time period below in which searches in Email Archive were unavailable. We have also confirmed that searches are currently functioning normally. ■ Incident period May 19, 2026, approximately 13:41–14:06 （JST） Please note that email archiving itself continued to operate normally during the above time period. We sincerely apologize for any inconvenience caused.

1. 23 aprilie 2026 la 07:40 UTCinvestigating

   現在、HENNGE One サポートおよび導入支援の電話受付窓口に一時的に繋がらない事象を確認しております。 電話受付システム側で調査および対応を実施しております。 恐れ入りますが、お急ぎの場合はメールまたは Webフォームよりお問い合わせ下さいますようお願い申し上げます。 ご迷惑をおかけしており申し訳ありません。 ----------------------------------- We are currently experiencing an issue where our phone lines for the HENNGE One Support and Onboarding desks are temporarily unavailable. An investigation and restoration efforts are currently underway by the phone system provider. In the meantime, we kindly ask that you contact us via email or Web-Form for any urgent inquiries. We sincerely apologize for the inconvenience caused.

2. 23 aprilie 2026 la 15:33 UTCresolved

   本件について続報です。 HENNGE One サポートおよび導入支援の電話受付窓口の電話受付窓口につきまして 正常に繋がるようになったことを確認いたしました。 ご迷惑をおかけしました事を深くお詫び申し上げます。 ----------------------------------- We are pleased to inform you that the issue affecting the phone lines for HENNGE One Support and the Onboarding desk has been resolved. We have confirmed that all lines are now connecting normally. We sincerely apologize for any inconvenience this may have caused and appreciate your patience.

1. 23 aprilie 2026 la 04:47 UTCidentified

   現在、HENNGE Access Control の管理画面にて SAML SSO 設定を行う際に特定の操作を行うとエラーが発生する事象を確認しております。 ■事象の発生条件と詳細 HENNGE Access Control 管理画面の [サービスプロバイダー設定] から SAML による SSO 設定を追加あるいは編集する際に、設定画面の項目 [属性の設定] で 「+ 属性の追加」をクリックすると、エラーが表示され設定することができない。 ※ [属性の設定] で追加の属性を設定しない場合は SAML SSO 設定を作成および変更可能です。 現在、システムチームにて調査および対応を実施しております。 ご迷惑をおかけしており申し訳ありません。 ----------------------------- We have identified an issue where an error occurs during specific operations when configuring SAML SSO in the HENNGE Access Control admin console. ■ Incident Conditions and Details When adding or editing SAML SSO settings under [Service Provider Settings], clicking "+ Add new attribute row" in the [Attribute Editor] section triggers an error, preventing the configuration from being saved. Note: Creating or modifying SAML SSO settings is still possible as long as no additional attributes are added in the [Attribute Editor]. Our engineering team is currently investigating the cause and working on a resolution. We sincerely apologize for any inconvenience this may cause.

2. 23 aprilie 2026 la 06:46 UTCresolved

   本件につきまして続報です。 システムチームにて修正が完了し、 [属性の設定] で 「+ 属性の追加」をクリックした際のエラーが解消されたことを確認いたしました。 本事象にて、SAML SSO 設定の作成や変更が行えなかったお客様は、お手数ですが再度お試し下さいますようお願い申し上げます。 ご迷惑をおかけしました事を深くお詫び申し上げます。 ----------------------------- Update on the ongoing issue: Our engineering team has completed the fix and confirmed that the error occurring when clicking "+ Add new attribute row" under [Attribute Settings] has been resolved. For customers who were unable to create or modify SAML SSO settings due to this issue, we kindly ask that you try again. We sincerely apologize for any inconvenience this may have caused.

1. 8 aprilie 2026 la 19:03 UTCinvestigating

   現在、HENNGE Email DLP において、Gmail からのメール配送に一部遅延が発生していることを確認しております。 本件につきましては、弊社システムチームにて Google 社への問い合わせを含め、詳細な調査を実施しております。 なお、本事象は Exchange Online からのメール配送には影響がないことを確認しております。 ご迷惑をおかけしておりますことをお詫び申し上げます。 ---------------------------------------------------------------- We have confirmed that there are partial delays in email delivery from Gmail within HENNGE Email DLP. Our system team is currently conducting a detailed investigation into this issue, including inquiries with Google. Please note that we have confirmed that this issue does not affect email delivery from Exchange Online. We sincerely apologize for any inconvenience caused.

2. 8 aprilie 2026 la 19:53 UTCinvestigating

   続報です。 Google 社におきましても、Gmail からのメール配送に一部遅延が発生している事象が確認されており、現在対応しております。 また、Google 社のステータスダッシュボードにも掲載されておりますので、ご確認ください。 https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT?hl=ja ---------------------------------------------------------------- Update: > This is a follow-up update. At Google, an issue involving delays in email delivery from Gmail has also been confirmed, and they are currently working to address it. This issue has also been posted on Google’s status dashboard, so we kindly ask that you review it. https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT?hl=en

3. 8 aprilie 2026 la 22:37 UTCmonitoring

   続報です。 Gmail のメール配送遅延につきまして、Google 社において対策が講じられたことを確認しております。 Google 社の対応状況につきましては、以下のステータスダッシュボードをご確認いただけますと幸いです。 https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT?hl=ja なお、弊社におきましても、引き続きシステムチームによる監視を行ってまいります。 ---------------------------------------------------------------- Update: > Regarding the Gmail email delivery delays, we have confirmed that Google has implemented countermeasures. For the latest status of Google’s response, please refer to the following status dashboard: https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT?hl=en We will continue to monitor the situation through our system team.

4. 8 aprilie 2026 la 23:12 UTCresolved

   本件につきまして、弊社サービス側でも Gmail からのメール受付および、Gmail 宛のメール配信ともに正常に行われていることを確認いたしました。 システム側でも異常は見られないため解消したと判断いたします。 本事象につきましては Gmail（Google）側のインシデントに起因したものとなりますので、恐れ入りますが詳細は Google 社へお問い合わせ下さいますようお願い申し上げます。 https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT?hl=ja ---------------------------------------------------------------- Regarding this issue, we have confirmed that both receiving emails from Gmail and delivering emails to Gmail are functioning normally on our service side. As no abnormalities are detected in our systems, we consider this matter resolved. This issue was caused by an incident on the Gmail (Google) side. For further details, we kindly ask that you contact Google directly. https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT?hl=en

1. 19 martie 2026 la 03:11 UTCidentified

   An Issue in HENNGE Email Archive: An Error May Occur When Performing a Search 現在 HENNGE Email Archive にて、一部のテナントでアーカイブの検索が行えない（実行するとエラーが表示される）事象を確認しております。 本件についてはシステム チームにて原因を特定し、対応を開始しております。 ご迷惑をおかけしており申し訳ありません。 なお、メールのアーカイブ処理自体は正常に行われておりますので、この点につきましてはご安心ください。 ---------------------------------------------------------------- We have confirmed an issue where archive searches cannot be performed (an error is displayed when executed) in some tenants on HENNGE Email Archive. Our system team has identified the cause and has begun working on a resolution. We sincerely apologize for the inconvenience caused. Please rest assured that the email archiving process itself is functioning normally.

2. 19 martie 2026 la 09:42 UTCidentified

   本件について続報です。 現在引き続き HENNGE Email Archive のシステム復旧に向けて対応を行っており、徐々に改善傾向にあることを確認しております。 引き続き完全復旧に向けて対応をすすめてまいります。 なお、本件につきまして影響は一部テナントのアーカイブ検索のみであり、新規メールのアーカイブ取得などに影響はございませんのでご安心下さい。 引き続きご迷惑をおかけしており申し訳ありません。 ------------------------------------------- Update on the ongoing issue: We are continuing our efforts to restore the HENNGE Email Archive system. We have confirmed that the situation is gradually improving. We will continue to work toward a full recovery. Please be assured that the impact of this incident is limited to archive searching for some tenants; there is no impact on the archiving of emails. We sincerely apologize for the continued inconvenience.

3. 23 martie 2026 la 00:26 UTCresolved

   本件につきまして続報です。 本事象につきまして、弊社システムチームにて対応を行い、復旧したことを確認いたしました。 なお、先日お伝えしたとおり、本件の影響範囲は一部テナントのアーカイブ検索のみに限られており、新規メールのアーカイブ取得などには影響はございませんでしたので、ご安心ください。 この度はご迷惑をおかけし申し訳ありませんでした。 ------------------------------------------- Update on the recent issue: Regarding this issue, our system team has taken corrective action and confirmed that the service has been restored. As previously mentioned, the impact of this issue was limited to archive searches in some tenants, and there was no impact on the archiving of new emails, so please rest assured. We sincerely apologize for any inconvenience caused.

1. 4 martie 2026 la 08:43 UTCinvestigating

   現在、一部のお客さまの HENNGE Access Control 環境にて HENNGE Device Certificate（デバイス証明書）の発行を行っても 「保留中」のステータスのまま処理が進まない事象を確認しております。 本件は現在システムチームにて調査中です。 ご迷惑をおかけしており申し訳ありません。 --------------------------------- We have identified an issue where HENNGE Device Certificate issuance for some customers is remaining in "Pending" status and failing to proceed. Our system team is currently investigating the cause of this matter. We apologize for any inconvenience this may cause.

2. 4 martie 2026 la 10:03 UTCresolved

   本件について続報です。 一部の環境でデバイス証明書の発行申請を行うと「保留中」のステータスのままになってしまう事象につきまして システムチームによる対応を実施いたしました。 HENNGE Access Control 管理画面の [ログ管理] > [デバイス証明書操作履歴] の画面で 「保留中」のまま処理が止まってしまっていた発行申請についてステータスが「エラー」に変更されております。 お手数ですが「エラー」と表示されている発行申請分につきましては、再度発行申請を実施くださいますようお願い申し上げます。 ご迷惑をおかけしました事を深くお詫び申し上げます。 --------------------------------- We are providing an update regarding the issue where some HENNGE Device Certificate issuance requests remained in "Pending" status. Our system team has completed the necessary actions to address this. For requests that were stuck in "Pending" status, the status has now been changed to "Error." You can verify this in the HENNGE Access Control Admin Console under [Log Management] > [Device Certificate Operations]. If your request is now showing as "Error," we kindly ask that you resubmit the issuance request. We sincerely apologize for the inconvenience this has caused.

1. 20 februarie 2026 la 08:34 UTCresolved

   HENNGE Access Control から Microsoft 365(Entra ID) へのクラウド同期につきまして 下記の通りの期間と内容の事象が発生しておりました。 なお、本事象によるログイン等のユーザー影響はございませんでしたのでご安心下さい。 ・期間 2026年2月19日12時〜2月20日16:00頃（JST） ・発生事象 定期同期（1時間毎）および手動同期の実行時、変更のないユーザーについても同期ログに 更新（Update） として出力される ご迷惑をおかけし申し訳ありません。 ----------------------------------------- We have identified and resolved an issue regarding the cloud synchronization between HENNGE Access Control and Microsoft 365(Entra ID). Please be assured that this incident had no impact on user logins or other authentication services. Period: Thursday, February 19, 2026, 12:00 PM – Friday, February 20, 2026, 4:00 PM (JST) Details: During both scheduled (hourly) and manual synchronizations, users with no changes were incorrectly recorded as "Update" in the synchronization logs. We apologize for any confusion or inconvenience this may have caused.

1. 9 februarie 2026 la 03:18 UTCidentified

   現在 HENNGE Email Archive にて、一部テナントでアーカイブの検索およびダウンロードが行えない（実行するとエラーが表示される）事象を確認しております。 システムチームにて原因を特定後、対応を開始しております。 ご迷惑をおかけしており申し訳ありません。 ------------------------------------------- We have identified an issue with HENNGE Email Archive where some tenants are currently unable to search for or download archives, resulting in an error message. Our engineering team has identified the cause and is currently working on a resolution. We apologize for any inconvenience this may cause.

2. 9 februarie 2026 la 05:20 UTCidentified

   本件について続報です。 現在引き続き HENNGE Email Archive のシステム復旧に向けて対応を行っており、徐々に改善傾向にあることを確認しております。 引き続き完全復旧に向けて対応をすすめてまいります。 なお、本件につきまして影響は一部テナントのアーカイブ検索のみであり、新規メールのアーカイブ取得などに影響はございませんのでご安心下さい。 引き続きご迷惑をおかけしており申し訳ありません。 ------------------------------------------- Update on the ongoing issue: We are continuing our efforts to restore the HENNGE Email Archive system. We have confirmed that the situation is gradually improving. We will continue to work toward a full recovery. Please be assured that the impact of this incident is limited to archive searching for some tenants; there is no impact on the archiving of emails. We sincerely apologize for the continued inconvenience.

3. 9 februarie 2026 la 09:48 UTCidentified

   本件について続報です。 現在引き続き HENNGE Email Archive のシステム復旧に向けて対応を行っており、ごく一部のテナントを除き事象が解消していることを確認しております。 完全復旧に向けて対応をすすめてまいります。 引き続きご迷惑をおかけしており申し訳ありません。 ------------------------------------------- Update: > We are continuing our restoration efforts for HENNGE Email Archive. We have confirmed that the issue has been resolved for the majority of tenants, with only a few exceptions remaining. We will continue to work toward a full recovery. We sincerely apologize for the ongoing inconvenience.

4. 12 februarie 2026 la 01:06 UTCresolved

   本件について続報です。 残りのごく一部の HENNGE Email Archive 環境につきましても対応を実施し、復旧したことを確認いたしました。 先日お伝えした通り、本件の影響は一部テナントのアーカイブ検索のみであり、新規メールのアーカイブ取得などに影響はございませんでした。 この度はご迷惑をおかけし申し訳ありませんでした。 ------------------------------------------- Update on the recent issue: We have completed the necessary actions for the remaining few HENNGE Email Archive environments and confirmed that they have been fully restored. As previously reported, this incident only affected the archive search function for certain tenants. There was no impact on the archiving of new incoming/outgoing emails. We sincerely apologize for any inconvenience caused.

1. 2 februarie 2026 la 10:50 UTCinvestigating

   現在 HENNGE Email DLP にてフィルタリング処理プロセスの遅延を確認しております。 これにより、Microsoft 365 および Google Workspace からメールを送信してから、保留や承認を確認するユーザーコンソールに表示されるまでや 宛先に送信されるまでに時間がかかる可能性があります。 現在、弊社システムチームにて調査および対応を行っております。 ご迷惑をおかけしており申し訳ありません。 ------------------------------------------ We are currently experiencing delays in the filtering process of HENNGE Email DLP. Due to this issue, there may be a delay between sending an email from Microsoft 365 or Google Workspace and its appearance in the user console for suspension or approval, as well as its final delivery to recipients. Our system team is currently investigating and working to resolve the issue. We apologize for any inconvenience this may cause.

2. 2 februarie 2026 la 11:19 UTCmonitoring

   本件について続報です。 システムチームによる対応を行い、現在は HENNGE Email DLP の遅延は解消し 正常にメールフィルタリングの処理が行われていることを確認いたしました。 現時点で確認しております、事象の発生時間と影響は下記のとおりです。 ・2026年2月2日18:30〜20:00頃 ・上記時間帯の間の10分〜15分程度 引き続き、システムチームによる監視を行ってまいります。 ご迷惑をおかけし申し訳ありません。 ------------------------------------------ This is a follow-up regarding the delay issue. Our system team has addressed the issue, and the delay in HENNGE Email DLP has been resolved. We have confirmed that email filtering is now processing normally. Incident Period and Impact: Time of occurrence: February 2, 2026, from approximately 18:30 to 20:00 (JST) Duration of impact: Approximately 10 to 15 minutes within the above timeframe The system team will continue to monitor the situation closely to ensure stability. We apologize for any inconvenience caused.

3. 2 februarie 2026 la 11:19 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 februarie 2026 la 04:01 UTCresolved

   本件につきまして、継続して監視を行っておりましたが再発等はなくサービスが正常に稼働していることを確認いたしました。 なお、本件によるメールのロスト等は発生しておりません。 この度はご迷惑をおかけし申し訳ありませんでした。 ------------------------------------------ We have completed our continuous monitoring of the system and can confirm that the service is operating normally with no recurrences. Our investigation has confirmed that no emails were lost as a result of this incident. We sincerely apologize for any inconvenience caused.

1. 14 ianuarie 2026 la 05:20 UTCinvestigating

   現在 HNENNGE File DLP にて Microsoft 365 の SharePoint Online のリスク検知に以下の問題が確認されております。 ・Microsoft 365 組織内全体公開のファイルが、外部公開ファイルとして誤って検知されてしまう これに伴い下記のような事象が発生する可能性がございます。 ・リスク検知が急増する ・外部公開ファイルの自動停止ポリシーを利用されている場合に誤ってファイルの公開リンクが削除される 現在、弊社システムチームにて調査および対応を行っております。 ご迷惑をおかけしており申し訳ありません。 ------------------------------------------- We have confirmed the following issue with risk detection for Microsoft 365 SharePoint Online in HENNGE File DLP: ・Files shared within the entire Microsoft 365 organization are being erroneously detected as externally shared files. As a result, the following incidents may occur: ・A sudden surge in risk detection alerts. ・For users with automatic remediation policies for externally shared files, public sharing links may be inadvertently deleted. Our system team is currently investigating and working on a resolution. We sincerely apologize for any inconvenience this may cause.

2. 14 ianuarie 2026 la 08:00 UTCmonitoring

   本件につきまして続報です。 システムチームによる対応が完了し、現時点で新たに誤検知が発生することはなくなったことを確認しております。 影響のあった期間は下記の通りです。 ・2026年1月8日12時9分〜1月14日13時43分ごろ また、本事象にて誤検知が行われ、自動停止ポリシーによって公開リンクが削除されてしまったファイルにつきまして システム側から再度同様の権限範囲（Microsoft 365 組織内のみ公開）の設定を行う予定でございます。 このリカバリによって、組織内の公開権限は事象発生以前の状態に戻りますが公開リンクの URL は変更されます。 SharePoint 上のフォルダからファイルにアクセスいただく場合には問題ありませんが、直接公開 URL にてファイルをご利用されている場合は、改めて公開 URL を共有し直して下さい。 上記のリカバリにつきましては完了後改めて、本ダッシュボードにてお知らせいたします。 ファイルの公開リンク復旧をお急ぎの場合は恐れ入りますが、手動で組織内公開を再度実施いただきますようお願い致します。 ご迷惑をおかけしており申し訳ありません。 ------------------------------------------- Here is a further update regarding this matter. The systems team has completed its response, and we have confirmed that no new misdetections are occurring at this time. The period during which this issue occurred is as follows: From approximately 12:09 PM on January 8, 2026, to 1:43 PM on January 14, 2026 (JST) Regarding the files that were misdetected and had their public links deleted by the Auto Remediation Policies, we are planning to restore the same level of access permissions (Internal/Organization-wide only) from the system side. Please note that while this recovery will restore the organization-wide access permissions to their original state, the URLs for the public links will be changed. There will be no issues when accessing files through SharePoint folders. However, if you use direct public URLs, please re-share the newly generated URLs. We will provide a further update on this dashboard once the recovery process is complete. If you are in a hurry to restore a file's public link, we kindly ask that you manually re-configure the organization-wide sharing settings yourself. We sincerely apologize for the continued inconvenience.

3. 19 ianuarie 2026 la 08:13 UTCresolved

   本件につきまして続報です。 本事象において誤検知が発生し、自動停止ポリシーにより公開リンクが削除されていたファイルにつきまして、 システム側にて同様の権限範囲（Microsoft 365 組織内のみ公開）となるよう、再設定によるリカバリ対応が完了しました。 なお、本リカバリ対応により、組織内での公開権限は事象発生前の状態に復旧しておりますが、公開リンクの URL は変更されております。 そのため、SharePoint 上のフォルダからファイルへアクセスされる場合には問題ありませんが、直接公開リンクにてファイルをご利用される場合は、改めて新たな公開 URL を共有し直して下さい。 この度はご迷惑をおかけしましたことを改めてお詫び申し上げます。 ------------------------------------------- Here is an update regarding this matter. In this incident, a false positive occurred, and as a result, the organization-scoped links for the affected file were removed by an automatic suspension policy. We have completed recovery actions on the system side by reconfiguring the file to restore the same permission scope as before (shared only within the Microsoft 365 organization). Please note that while the internal sharing permissions have been restored to their pre-incident state, the organization-scoped links have changed as a result of this recovery. Accordingly, there is no issue when accessing the file via its folder in SharePoint; however, if you access the file directly using organization-scoped links, please share the newly generated URL again. We sincerely apologize again for the inconvenience this has caused.

1. 17 decembrie 2025 la 01:38 UTCinvestigating

   現在 Box 側の障害に起因して、HENNGE Secure Download for Box に遅延が発生していることを確認しております。 ■Boxのステータスダッシュボード https://status.box.com/incidents/48t1p9xtd4tz 本件につきまして Box 側での対応状況および、HENNGE Secure Download for Box 側の状況について 弊社開発部門でも確認を進めております。 −−−−−−−−−−−−−−−−−−−−−−−−−−− We have confirmed that the HENNGE Secure Download for Box service is currently experiencing delays due to an ongoing outage on the Box side. ■ Box Status Dashboard https://status.box.com/incidents/48t1p9xtd4tz Our development team is currently investigating both the status of the response from Box and the resulting situation regarding HENNGE Secure Download for Box.

2. 17 decembrie 2025 la 03:49 UTCmonitoring

   本件につきまして続報です。 Box側で対応が行われ、弊社側でも HENNGE Secure Download for Box にて遅延していたすべてのメールが処理されたことを確認いたしました。 引き続き再発等がないか状況を監視しております。 −−−−−−−−−−−−−−−−−−−−−−−−−−− Here is an update regarding this matter. The necessary action was taken by Box, and we have also confirmed on our side that all emails that were delayed in HENNGE Secure Download for Box have been processed. We will continue to monitor the situation for any potential recurrence.

3. 17 decembrie 2025 la 04:49 UTCresolved

   本件につきまして、継続して監視を行っておりましたが再発等はなくサービスが正常に稼働していることを確認いたしました。 なお遅延しておりました HENNGE Secure Download for Box をご利用のメールにつきましては すべて正常に処理が完了しており、本事象の影響によるメールのロストやバウンス等は発生しておりません。 ※ メール宛先側の問題などによるその他のバウンスは含まれません。 この度はご迷惑をおかけし申し訳ありません。 −−−−−−−−−−−−−−−−−−−−−−−−−−− We have been continuously monitoring this matter and have confirmed that the service is operating normally with no recurrence of the issue. Furthermore, all emails using HENNGE Secure Download for Box that were previously delayed have been processed successfully, and no bounces occurred due to the impact of this incident. *This does not include other bounces caused by issues on the recipient's mail server side. We sincerely apologize for the inconvenience this has caused.

1. 3 decembrie 2025 la 01:32 UTCinvestigating

   現在 HENNGE Cloud Protecton サービスにて特定 URL が誤って検知される事象を確認しており、詳細につきまして調査中です。 ------------------------------------------- We are currently investigating an issue with the HENNGE Cloud Protecton service where a specific URL is being incorrectly detected, and details are under investigation.

2. 3 decembrie 2025 la 02:29 UTCinvestigating

   本件につきまして続報です。 現在も詳細につきましては WithSecure社 と協力して調査中となります。 現時点で弊社にて確認している範囲となりますが一時的な回避策として HENNGE Cloud Protection のポリシー [Exchange] > [URLスキャン] > [信頼済みのWebサイト] の設定をオンにしていただき 下記の URL を信頼済みに設定いただくことで回避できる可能性がございますので、お試しいただけますと幸いでございます。 ・https://aka.ms/LearnAboutSenderIdentification ・https://aka.ms/o0ukef ご迷惑をおかけしており申し訳ありません。 ------------------------------------------- Here is an update regarding this matter. We are currently continuing to investigate the details in cooperation with WithSecure. While we are still in the process of confirming the full scope of the issue, we have identified a potential temporary workaround: Could you please enable the setting for "Trusted Websites" within the HENNGE Cloud Protection policy under [Exchange] > [URL Scanning] , and add the following URLs to the trusted list? ・https://aka.ms/LearnAboutSenderIdentification ・https://aka.ms/o0ukef We kindly ask you to try this workaround. We apologize for the inconvenience this is causing you."

3. 3 decembrie 2025 la 05:14 UTCmonitoring

   本件につきまして続報です。 WithSecure社による対応が行われ、現在は Microsoft 関連の URL が誤って検知される事象は解消したことを確認いたしました。 誤って検知されてしまったメールなどのアイテムが隔離されている場合につきまして、一括で解放する手段などについては現在 WithSecure社へ確認を行っております。 恐れ入りますがお急ぎの場合は管理画面から解放の操作を実施くださいますようお願い致します。 この度はご迷惑をおかけしましたことをお詫び申し上げます。 ------------------------------------------- Here is a follow-up report regarding this matter. We have confirmed that the issue where Microsoft-related URLs were incorrectly detected has been resolved, following remediation by WithSecure. Regarding items such as emails that were incorrectly quarantined, we are currently checking with WithSecure about methods, such as bulk release, to restore them. We apologize, but if this is urgent, please carry out the release operation from the administration screen. We sincerely apologize for the inconvenience this has caused.

4. 5 decembrie 2025 la 01:02 UTCmonitoring

   本件につきまして続報です。 誤って検知され隔離されてしまったメールなどのアイテムにつきまして WithSecure 社側で一括解放を実施いたします。 ※本事象の対象となった、誤って隔離されたアイテム以外の解放は行われませんのでご安心ください。 ■解放処理実施日時 12月5日（金）21時以降より順次解放 解放の完了までにはお時間を頂く可能性がございます。あらかじめご承知おきくださいますと幸いです。 この度はご迷惑をおかけしましたことを改めてお詫び申し上げます。 ------------------------------------------- Here is an update regarding this matter. WithSecure will collectively release the quarantined items, such as emails, that were erroneously detected and isolated. *Please be assured that no items other than those erroneously quarantined items affected by this incident will be released. ■ Release Processing Schedule The release process will be implemented sequentially starting after 9:00 PM on Friday, December 5th (Japan Time). Please note that it may take some time for the release process to be fully completed. We apologize once again for the inconvenience this has caused.

5. 8 decembrie 2025 la 02:29 UTCresolved

   本件につきまして続報です。 誤って検知され隔離されてしまったメールなどのアイテムにつきまして WithSecure 社側で一括解放を実施し、解放が完了していることを確認しております。 この度はご迷惑をおかけしましたことを改めてお詫び申し上げます。 ------------------------------------------- Here is an update regarding this matter. We have confirmed that WithSecure has completed the bulk release of the quarantined items, such as emails, that were erroneously detected and isolated. We sincerely apologize again for the inconvenience this has caused.

1. 2 decembrie 2025 la 08:56 UTCinvestigating

   現在 HENNGE Cloud Protection にて Microsoft Teams の招待メールや予定表が誤って検知される事象を確認しております。 現在 WitSecure 社と協力して調査・対応を実施しております。 HENNGE Cloud Protection のポリシー [Exchange] > [URLスキャン] >[信頼済みのWebサイト] の設定で機能をオンにしていただき、下記の URL を信頼済みに設定いただくことで回避できることがあるようですので、お試しいただけますと幸いでございます。 ・http://invite_block.action.help/ ・http://meet_invite_block.action.help/ ・http://x_meet_invite_block.action.help/ また本事象は WitSecure社のステータスダッシュボードにも掲載されております。 あわせてご確認くださいますと幸いでございます。 https://status.withsecure.com/incidents/xvghr46ggd8d ご迷惑をおかけしており申し訳ありません。 ---------------------------------------------- We are currently confirming an issue in HENNGE Cloud Protection where Microsoft Teams invitation emails and calendar items are being incorrectly flagged/detected. We are actively investigating and working on a resolution in cooperation with WitSecure. This issue may be mitigated by adding the following URLs to the trusted list in the HENNGE Cloud Protection policy settings: [Exchange] > [URL Scanning] > [Trusted Websites]. We would appreciate it if you could try this workaround. ・http://invite_block.action.help/ ・http://meet_invite_block.action.help/ ・http://x_meet_invite_block.action.help/ Furthermore, this incident has been posted on WitSecure's status dashboard. We kindly ask you to check it as well. https://status.withsecure.com/incidents/xvghr46ggd8d We sincerely apologize for any inconvenience this may be causing.

2. 2 decembrie 2025 la 10:41 UTCresolved

   本件につきまして続報です。 WitSecure社による対応が行われ、現在は Microsoft Teams の招待メールや予定表が誤って検知される事象は解消したことを確認いたしました。 誤って検知されてしまったメールや予定表につきましては、恐れ入りますが管理画面から解放の操作を実施くださいますようお願い致します。 この度はご迷惑をおかけしましたことをお詫び申し上げます。 ---------------------------------------------- Here is an update regarding this matter. We have confirmed that the issue where Microsoft Teams invitation emails and calendar items were being incorrectly flagged has been resolved following the action taken by WitSecure. Regarding the emails and calendar items that were incorrectly flagged, we kindly ask you to release them via the administration screen. We apologize for the inconvenience this has caused.

1. 1 decembrie 2025 la 01:39 UTCidentified

   HENNGE File DLP 管理コンソール上のダッシュボードが表示されない問題を検知しました。 現在、システムチームにて復旧に向けて取り組んでいます。 ご迷惑をおかけしておりますこと、お詫び申し上げます。 ---------------------------------------------------------- We are currently experiencing an issue where the HENNGE File DLP Admin Console dashboard fails to load. The engineering team is actively working on a fix. We sincerely apologize for the inconvenience.

2. 1 decembrie 2025 la 02:32 UTCmonitoring

   本件につきまして続報です。 HENNGE File DLP 管理コンソール上のダッシュボードが表示されない事象につきまして、原因の特定、対応が完了し、現在は正常に処理が行われることを確認しております。 またダッシュボードの表示以外の影響は現在確認されておりません。 本件、ご迷惑をおかけしました事をお詫び申し上げます。 ---------------------------------------------------------- Here is an update regarding this matter. We have identified the cause of the issue where the dashboard on HENNGE File DLP management console was not displaying, and the necessary fixes have been completed. We have confirmed that the system is now functioning normally. Additionally, we have not identified any impacts other than the dashboard display issue at this time. We sincerely apologize for any inconvenience this matter has caused.

3. 1 decembrie 2025 la 07:32 UTCresolved

   This incident has been resolved.