HULFT Square Outage History
HULFT Square is up right nowPingoru has recorded 24 incidents for HULFT Square: 1 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 4 of 511 (1%) |
Incidents, newest first
Major October 16, 2026 Some screens in HULFT Square cannot be viewed. 3h 46m HULFT Square
Started Oct 16, 2026, 09:46 AM UTC· resolved Oct 16, 2026, 01:32 PM UTC
- investigating Oct 16, 2026, 09:46 AM UTC
The profile, service plan, and App Square pages are currently not viewable. Also, an error is displayed when the dashboard is shown. We apologize for any inconvenience caused. Please wait until the failure is recovered.
- investigating Oct 16, 2026, 01:10 PM UTC
We are continuing to work toward a resolution. We apologize for the inconvenience.
- resolved Oct 16, 2026, 01:32 PM UTC
We have implemented countermeasures and confirmed that the issue that had been occurring has been resolved. We apologize for the inconvenience this has caused.
Critical July 15, 2025 The File Event Jobs are down. 25m File Event Jobs
Started Jul 15, 2025, 06:26 PM UTC· resolved Jul 15, 2025, 06:52 PM UTC
- investigating Jul 15, 2025, 06:26 PM UTC
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.
- resolved Jul 15, 2025, 06:52 PM UTC
This incident occurred at 03:25 and was resolved at 03:30. There was no impact on customers.
Notice July 3, 2025 一部環境でスケジュールジョブが起動しない/Scheduled job does not start in some environments – Schedule Jobs
Started Jul 03, 2025, 09:31 AM UTC· resolved Jul 03, 2025, 09:31 AM UTC
- resolved Jul 03, 2025, 09:31 AM UTC
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..
Critical May 22, 2025 The Schedule Jobs are down. 3h 33m Schedule Jobs
Started May 22, 2025, 01:41 AM UTC· resolved May 22, 2025, 05:15 AM UTC
- investigating May 22, 2025, 01:41 AM UTC
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.
- resolved May 22, 2025, 01:55 AM UTC
This incident occurred at 10:30 and was resolved at 11:20. There was no impact on customers.
Critical April 3, 2025 スケジュールジョブが起動しない/Scheduled job does not start 25m Schedule Jobs
Started Apr 03, 2025, 04:01 AM UTC· resolved Apr 03, 2025, 04:26 AM UTC
- investigating Apr 03, 2025, 04:01 AM UTC
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.
- resolved Apr 03, 2025, 04:26 AM UTC
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.
Critical March 16, 2025 The HULFT Transfer Jobs are down. 18m HULFT Transfer Jobs
Started Mar 16, 2025, 12:43 PM UTC· resolved Mar 16, 2025, 01:02 PM UTC
- investigating Mar 16, 2025, 12:43 PM UTC
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.
- resolved Mar 16, 2025, 01:02 PM UTC
This incident occurred at 21:42 and was resolved at 21:47. There was no impact on customers.