| Recurring |
unknown |
(a) The software failure incident at Redfin seems to be a unique occurrence for the company as there is no mention in the article of a similar incident happening before within the same organization or with its products and services. The statement from Redfin mentioned that they don't know yet what caused the initial problem and are looking into it, indicating that it may be a new issue for them [13802].
(b) The article does not provide any information about similar incidents happening at other organizations or with their products and services. Therefore, it is unknown if this type of software failure has occurred elsewhere. |
| Phase (Design/Operation) |
design |
(a) The software failure incident at Redfin was related to the design phase. The article mentions that the site's recent redesign was not the cause of the issue. Instead, the master database machine crashed, and the fallback to a different master failed, indicating a failure introduced by system development or updates [13802].
(b) The software failure incident at Redfin was not related to the operation phase. There is no mention in the article of the failure being caused by the operation or misuse of the system. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident at Redfin was due to issues within the system. The article mentions that the master database machine crashed, and the fallback to a different master failed, leading to the site being down for about four hours. Additionally, the backup procedure was more time-consuming, indicating internal system issues [13802]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident at Redfin was attributed to non-human actions. The article mentions that the master database machine crashed, and the fallback to a different master failed, leading to the site being down for about four hours. The issue was not related to the new page design but rather a technical failure with the database system [13802]. |
| Dimension (Hardware/Software) |
hardware |
(a) The software failure incident at Redfin was attributed to hardware issues. The master database machine crashed, and the fallback to a different master failed, leading to the site being down for about four hours [13802]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident at Redfin was non-malicious. The article mentions that the site went down for several hours on a Saturday morning due to a master database machine crash and a failure in the fallback procedure, which was not related to the new page design. Redfin stated that they were investigating the cause of the initial problem, indicating that it was not a deliberate act to harm the system [13802]. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The software failure incident at Redfin was not due to poor decisions but rather an unexpected technical issue. The company mentioned that the site's downtime was caused by the master database machine crashing and the fallback to a different master failing, leading to a more time-consuming backup procedure. They also stated that they were investigating the root cause of the problem [13802]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident at Redfin was not attributed to development incompetence. The article mentions that the site went down for several hours on a Saturday morning due to the master database machine crashing and the fallback to a different master failing. The incident was described as a technical issue rather than a result of development incompetence [13802].
(b) The software failure incident at Redfin was categorized as accidental. The article states that the master database machine crashed, and the fallback to a different master failed, leading to the site being down for about four hours. The company mentioned that they were unsure about the initial cause of the problem but were investigating it [13802]. |
| Duration |
temporary |
The software failure incident at Redfin was temporary. The site was down for about four hours, from 4:15 a.m. to about 8:15 a.m. PT, due to the master database machine crashing and the fallback to a different master failing. The next backup procedure was more time-consuming, indicating that the issue was resolved within a few hours [13802]. |
| Behaviour |
crash, other |
(a) crash: The software failure incident at Redfin was a crash where the master database machine crashed, leading to the site being down for about four hours [13802].
(b) omission: There is no specific mention of the software failure incident being due to the system omitting to perform its intended functions at an instance(s) in the provided article.
(c) timing: The software failure incident was not related to the system performing its intended functions too late or too early [13802].
(d) value: The software failure incident was not due to the system performing its intended functions incorrectly [13802].
(e) byzantine: The software failure incident did not involve the system behaving erroneously with inconsistent responses and interactions [13802].
(f) other: The software failure incident was specifically described as a crash related to the master database machine failure and the subsequent backup procedure being time-consuming [13802]. |