HULFT Square had 5 outages in the last 2 years totaling 4h 43m of downtime — averaging 0.2 incidents per month.
There were 5 HULFT Square outages since November 3, 2024 totaling 4h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
The File Event Jobs are currently unavailable. But script execution using Designer is still available. We apologize for any inconvenience caused. Please wait until the failure is recovered.
This incident occurred at 03:25 and was resolved at 03:30. There was no impact on customers.
2025年7月3日14時02分から14時24分(日本時間)にスケジュールジョブが一部環境において正常に起動しない事象が発生しました。 14時25分に復旧したことを確認いたしました。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ The scheduled job failed to start successfully in some environments on July 3, 2025, from 02:02 p.m. to 02:24 p.m. (Japan Standard Time). We have confirmed that the problem was resolved at 02:25 p.m..
The Schedule Jobs are currently unavailable. But script execution using Designer is still available. We apologize for any inconvenience caused. Please wait until the failure is recovered.
This incident occurred at 10:30 and was resolved at 11:20. There was no impact on customers.
2025年4月3日9時51分(日本時間)よりスケジュールジョブが正常に起動しない事象が発生しており継続中です。 現在原因調査中でございます。 引き続き調査を行い、定期的に状況報告させていただきます。 =＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ Since April 3, 2025, 9:51 a.m. (Japan Standard Time), scheduled jobs have not started properly, and the problem is ongoing. We are currently investigating the cause. We will continue to investigate and report the status periodically.
2025年4月3日9時51分(日本時間)よりスケジュールジョブが正常に起動しない事象ですが、 13時9分に復旧したことを確認いたしました。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ The event that the scheduled job did not start normally from 9:51 a.m. on April 3, 2025 (Japan Standard Time), We have confirmed that the problem was resolved at 13:09.
The HULFT Transfer Jobs are currently unavailable. But script execution using Designer is still available. We apologize for any inconvenience caused. Please wait until the failure is recovered.
This incident occurred at 21:42 and was resolved at 21:47. There was no impact on customers.