Cloud-Service System Failures
First written in FY2018. 4 of 8 entries say "Restated". Latest entry: FY2026.
The whole theme swung hardest in 2026: 16 of 83 companies on the "Worse" side.
5 other companies' latest entry also says "Reframed".
- FY2026ReframedAnnual report
「We are working to ensure stable system operation and rapid recovery by establishing 24-hour monitoring, adding system redundancy, performing backups and maintaining a recovery framework for system failures. However, if a system failure occurs and disrupts service delivery, our performance may be affected by reductions in service fees under service-level agreements (SLAs), among other factors.」
The company specifies countermeasures for system failures, including redundancy, backups and recovery procedures, and identifies reductions in usage fees under SLAs as an impact. - 2026-08-12MitigatedInvestor presentation
「Strengthened its BCP framework by establishing an alternative cloud environment at a physically separate location to protect data from natural disasters and cyberattacks and enable early service recovery and continuity.」
The company reported strengthening its BCP framework, including an alternative environment and early recovery, in response to the risks of cloud service disruptions and cyberattacks. - FY2025RestatedAnnual report
「System failures may occur as a result of increased server loads caused by temporary access congestion, hardware or software defects, human error, computer viruses, natural disasters, accidents, cyberattacks and other factors.」
The previously identified risks, including cyberattacks, are reiterated as causes of cloud service system failures. - FY2023WorsenedAnnual report
「System failures may occur as a result of increased server loads caused by temporary access congestion, hardware or software defects, human error, computer viruses, natural disasters, accidents, cyberattacks and other factors.」
Cyberattacks are explicitly added to the previous system failure factors, expanding the scope of risks associated with cloud service outages. - FY2022RestatedAnnual report
「We have established a 24-hour monitoring system and implemented measures to ensure stable system operations in preparation for such failures. However, if a system failure occurs and disrupts service provision, it may affect the performance of our group.」
The risks of system failures in cloud services and countermeasures such as 24-hour monitoring are reiterated. - FY2020RestatedAnnual report
「We have established a 24-hour monitoring system and implemented measures to ensure stable system operations in preparation for such failures. However, if a system failure occurs and disrupts service provision, it may affect the performance of our group.」
The risks of system failures in cloud services and countermeasures such as 24-hour monitoring are reiterated. - FY2019RestatedAnnual report
「We have established a 24-hour monitoring system and implemented measures to ensure stable system operations in preparation for such failures. However, if a system failure occurs and disrupts service provision, it may affect the performance of our group.」
The risks of system failures in cloud services and countermeasures such as 24-hour monitoring are reiterated. - FY2018First statedAnnual report
「System failures may occur as a result of increased server loads caused by temporary access congestion, hardware or software defects, human error, computer viruses, natural disasters, accidents, unauthorized external intrusion and other factors.」
The causes of system failures are listed, and the company states that it has a 24-hour monitoring system and measures in place to ensure stable operations.