| Recurring |
one_organization, multiple_organization |
(a) The software failure incident having happened again at one_organization:
Tele2, Sweden's second-largest telecoms company, experienced three crippling outages in the last 12 months, with the most recent outage occurring on June 17-19 [87940]. The company mentioned that the issue arose due to a combination of hardware and software faults affecting fixed, mobile, and IP-based calls.
(b) The software failure incident having happened again at multiple_organization:
The Dutch government launched an inquiry into an outage at telecoms company KPN in the Netherlands, which also knocked out emergency service numbers for nearly four hours. KPN blamed the outage on a software error [87940]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident at Tele2 in Sweden was attributed to a combination of hardware and software faults, indicating a failure related to the design phase of the system development. The company mentioned that the issue affected fixed, mobile, and IP-based calls, pointing towards underlying design flaws in the system [87940].
(b) The article did not provide specific information about the software failure incident at Tele2 being related to operation factors. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident at Tele2 in Sweden was attributed to a combination of hardware and software faults within the system. The Tele2 spokesman mentioned that the issue affected fixed, mobile, and IP-based calls, indicating an internal system failure [87940].
(b) outside_system: The CEO of Tele2, Anders Nilsson, clarified that the issue was not due to a cyber attack or security breach, suggesting that the failure did not originate from an external source [87940]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident at Tele2 in Sweden was attributed to a combination of hardware and software faults, indicating a non-human action as the contributing factor [87940].
(b) The CEO of Tele2, Anders Nilsson, clarified that the issue was not due to a cyber attack or security breach, suggesting that the failure was not caused by human actions [87940]. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident at Tele2 in Sweden was attributed to a combination of hardware and software faults [87940]. The article mentions that the issue arose due to a combination of hardware and software faults affecting fixed, mobile, and IP-based calls. CEO Anders Nilsson clarified that the issue was not due to a cyber attack or security breach.
(b) The software failure incident at KPN in the Netherlands was blamed on a software error [87940]. The article states that the Dutch government launched an inquiry into the outage at KPN, which knocked out emergency service numbers for nearly four hours. KPN attributed the outage to a software error. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The articles mention that the software failure incident at Tele2 in Sweden was not due to a cyber attack or security breach, indicating that the failure was non-malicious in nature [87940]. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The software failure incident at Tele2 in Sweden was not due to a cyber attack or security breach, as confirmed by CEO Anders Nilsson [87940]. This indicates that the failure was not a result of poor decisions related to cybersecurity measures.
(b) The article mentions that the issue at Tele2 arose due to a combination of hardware and software faults, affecting fixed, mobile, and IP-based calls. This suggests that the failure was more likely due to accidental decisions or mistakes rather than intentional poor decisions [87940]. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident at Tele2 in Sweden was attributed to a combination of hardware and software faults, indicating a potential issue related to development incompetence [87940].
(b) The article did not mention any information suggesting that the software failure incident was accidental. |
| Duration |
temporary |
(a) The software failure incident mentioned in the articles was temporary. It caused a national network outage at telecoms company Tele2 in Sweden, knocking out voice calls for many private customers and companies for several hours [87940]. The outage lasted from June 17-19, indicating a temporary disruption rather than a permanent one. |
| Behaviour |
crash, other |
(a) crash: The software failure incident at Tele2 in Sweden was described as a crash where the network outage caused voice calls to be knocked out for many private customers and companies for several hours [87940].
(b) omission: The article did not specifically mention the software failure incident as an omission where the system omitted to perform its intended functions at an instance(s).
(c) timing: The article did not specifically mention the software failure incident as a timing issue where the system performed its intended functions correctly, but too late or too early.
(d) value: The software failure incident at Tele2 in Sweden was not attributed to the system performing its intended functions incorrectly [87940].
(e) byzantine: The article did not mention the software failure incident as a byzantine failure where the system behaves erroneously with inconsistent responses and interactions.
(f) other: The software failure incident at Tele2 in Sweden was described as a combination of hardware and software faults affecting fixed, mobile, and IP-based calls, leading to the network outage [87940]. |