All Systems Operational

HENNGE Access Control Operational
HENNGE Secure Browser Operational
HENNGE Connect Operational
HENNGE Email DLP Operational
HENNGE Secure Transfer Operational
HENNGE Email Archive Operational
HENNGE File DLP Operational
HENNGE Cloud Protection Operational
HENNGE Tadrill Operational
Other Services Operational
Google Workspace Operational
Microsoft 365 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Sep 19, 2025

No incidents reported today.

Sep 18, 2025

No incidents reported.

Sep 17, 2025

No incidents reported.

Sep 16, 2025

No incidents reported.

Sep 15, 2025

No incidents reported.

Sep 14, 2025

No incidents reported.

Sep 13, 2025

No incidents reported.

Sep 12, 2025
An Issue by HENNGE Email DLP: Email Blacklisting
Resolved - 本件について続報です。

HENNGE Email DLP からの送信メールが RBL誤登録により宛先で受信拒否される事象につきまして解消したことを確認いたしました。
現時点で新たな受信拒否は発生していないことを確認しております。

なお、事象発生中に受信拒否されたメールにつきましては自動的に再送は行われませんので、恐れ入りますが手動での再送をお願いいたします。
また、HENNGE Email DLP の切り離しを実施された場合は再接続の実施もお願いいたします。


引き続きメールが拒否されており改善が見られない場合は、HENNGE One サポート窓口までご連絡くださいますと幸いです。
本件、ご迷惑をおかけしました事を深くお詫び申し上げます。


------------------------
Here is a follow-up on this matter.

We have confirmed that the issue of emails sent from HENNGE Email DLP being rejected by recipients due to incorrect RBL listings has been resolved. We have not observed any new rejections at this time.

Please note that emails that were rejected during the incident will not be resent automatically. We kindly ask you to resend them manually. Also, if you temporarily disconnected HENNGE Email DLP, please reconnect it.

If you are still experiencing email rejections and see no improvement, please contact the HENNGE One support team.

We sincerely apologize for any inconvenience this may have caused.
Sep 12, 12:44 JST
Investigating - 現在、HENNGE Email DLP によるメール配送について RBL 等への誤登録により、送信先で受信拒否される事象を確認しております。

弊社システムチームにて調査を実施し、対象の RBL側へ解除の申請などをすすめております。

本事象にて受信が拒否された場合下記のようなエラーメッセージが記載された、配信不能通知を受信することがございます。

■パターン1
said: 550 5.7.1 Service unavailable; client [IPアドレス] blocked using Cloudmark Sender Intelligence (Visit https://csi.cloudmark.com/reset-request/ if you feel this is in error.)

■パターン2
said: 550 5.7.1 Service unavailable; Client host [IPアドレス] blocked using gmo-rbl.jp; Poor Reputation Sender


緊急度合いが大きい場合には Microsoft 365 / Google Workspace から HENNGE Email DLP を
一時的に切り離すことも、ご必要に応じてご検討いただけますと幸いです。
※切り離しを実施している間のメールは HENNGE Email DLP によるフィルター処理や添付ファイルの ZIP 暗号化、URL 化は行われませんのでご注意ください

▽[Email DLP] 一時的な切り戻し方法 (Microsoft 365)
https://support.hdeone.com/hc/ja/articles/29802542824601

▽[Email DLP] 一時的な切り戻し方法 (Google Workspace)
https://support.hdeone.com/hc/ja/articles/29803863509657


ご迷惑をおかけしており恐れ入りますが、何卒よろしくお願いいたします。


------------------------
We have confirmed that emails sent via HENNGE Email DLP are being rejected by recipients due to their registration on RBLs (Real-time Blackhole Lists).

Our systems team is currently investigating this issue and is in the process of submitting removal requests to the relevant RBLs.

When an email is rejected due to this issue, you may receive a delivery failure notification containing an error message like one of the following:

■Pattern 1
said: 550 5.7.1 Service unavailable; client [IP address] blocked using Cloudmark Sender Intelligence (Visit https://csi.cloudmark.com/reset-request/ if you feel this is in error.)

■Pattern 2
said: 550 5.7.1 Service unavailable; Client host [IP address] blocked using gmo-rbl.jp; Poor Reputation Sender

If the issue is urgent, you may want to consider temporarily disconnecting HENNGE Email DLP from Microsoft 365 / Google Workspace.
Please note that during this period, emails will not be filtered, and attachments will not be ZIP-encrypted or URL-converted by HENNGE Email DLP.

▽[Email DLP] Temporary Reversion Method (Microsoft 365)
https://support.hdeone.com/hc/en-us/articles/29802542824601

▽[Email DLP] Temporary Reversion Method (Google Workspace)
https://support.hdeone.com/hc/en-us/articles/29803863509657

We apologize for any inconvenience this may cause and appreciate your understanding.
Sep 12, 12:21 JST
Sep 11, 2025

No incidents reported.

Sep 10, 2025

No incidents reported.

Sep 9, 2025

No incidents reported.

Sep 8, 2025

No incidents reported.

Sep 7, 2025

No incidents reported.

Sep 6, 2025

No incidents reported.

Sep 5, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage