Incident: iPhone XR O2 Network Connectivity Issue Impacting Calls and Data

Published Date: 2020-01-07

Postmortem Analysis
Timeline 1. The software failure incident affecting iPhone XR on O2's network happened in December 2019 [94872].
System 1. iPhone XR 2. O2 network 3. iOS software update [94872]
Responsible Organization 1. Apple [94872] 2. O2 [94872]
Impacted Organization 1. O2 customers [94872]
Software Causes 1. The software cause of the failure incident was an issue introduced with a recent update to the iPhone's iOS software, as reported by O2 customer Jim Buckley [94872].
Non-software Causes 1. Weak signal reception on O2's network affecting iPhone XR users [94872] 2. Network issue noticed by customers since a specific date (16 December) [94872] 3. Apple introducing the issue with a recent update to the iPhone's iOS software [94872]
Impacts 1. Many O2 customers experienced complete loss of signal several times a day, leading to the inability to make and receive calls, send and receive texts, and access a reliable 4G internet connection [94872]. 2. Customers had to resort to turning their phones off and on again as a temporary fix for the issue [94872]. 3. Some customers had to purchase alternative phones, like a second-hand iPhone 7, to ensure they remained contactable in case of emergencies [94872]. 4. The software failure incident caused inconvenience and frustration among affected customers, impacting their daily communication and internet usage [94872].
Preventions 1. Thorough testing of software updates before releasing them to the public could have prevented the software failure incident [94872]. 2. Implementing a more robust quality assurance process to catch network connectivity issues before they impact customers could have helped prevent the incident [94872]. 3. Conducting more extensive compatibility testing between Apple's iOS software updates and network providers like O2 could have identified and resolved potential issues before affecting users [94872].
Fixes 1. Turning the phone off and on again temporarily fixed the problem, according to O2 [94872]. 2. Apple mentioned that the issue will be resolved in a new software release [94872].
References 1. O2 spokeswoman 2. Apple 3. O2 customer Jim Buckley 4. Twitter (for customer complaints and responses) 5. BBC News

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to the iPhone XR losing signal on O2's network has happened again within the same organization. O2 customer Jim Buckley mentioned that he first noticed the network issue on 16 December and had virtually no signal since then. He mentioned that O2 had told him Apple introduced the issue with a recent update to the iPhone's iOS software, indicating a recurrence of the problem within Apple's products [94872]. (b) The incident has also affected multiple organizations as it impacted O2's network, which is a separate entity from Apple. O2 and Apple are working together to resolve the issue affecting O2 customers using the iPhone XR, indicating a cross-organization impact [94872].
Phase (Design/Operation) design (a) The software failure incident in the article is related to the design phase. O2 customer Jim Buckley mentioned that O2 had told him Apple had introduced the issue with a recent update to the iPhone's iOS software, indicating that the problem was caused by a software update introduced by Apple during the development phase [94872]. Additionally, Apple acknowledged the issue and stated that it would be resolved in a new software release, further confirming that the problem stemmed from the development phase [94872]. (b) There is no specific information in the articles indicating that the software failure incident was related to the operation phase or misuse of the system.
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the iPhone XR's connectivity issues on O2's network was attributed to an issue caused by a recent update to the iPhone's iOS software introduced by Apple [94872]. This indicates that the failure originated from within the system, specifically due to the software update released by Apple.
Nature (Human/Non-human) non-human_actions (a) The software failure incident in the article is related to non-human_actions. The issue affecting some O2 customers using iPhone XR was caused by an intermittent network connectivity problem, which Apple stated would be resolved in an upcoming software release [94872]. This indicates that the failure was due to factors introduced without human participation, such as a software bug or glitch.
Dimension (Hardware/Software) hardware, software (a) The software failure incident related to hardware: - The article mentions that O2 customer Jim Buckley noticed a network issue on his iPhone XR on 16 December, and he had virtually no signal since then. He resorted to buying a second-hand iPhone 7 as a backup due to the signal issue affecting his ability to be contactable in case of an emergency at his son's school [94872]. (b) The software failure incident related to software: - Both Apple and O2 acknowledged the issue affecting some iPhone XR users on O2's network, with Apple stating that the problem causing intermittent network connectivity will be fixed in an upcoming software release [94872].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to the iPhone XR on O2's network does not appear to be malicious. It was mentioned that the issue causing intermittent network connectivity for some O2 customers was due to a software problem introduced by Apple with a recent update to the iPhone's iOS software [94872]. Apple and O2 both acknowledged the issue and mentioned that it would be resolved in an upcoming software release, indicating that the problem was unintentional and not introduced with the intent to harm the system.
Intent (Poor/Accidental Decisions) poor_decisions (a) The software failure incident related to the iPhone XR's connectivity issue on O2's network seems to be more aligned with poor_decisions. O2 customer Jim Buckley mentioned that O2 had told him Apple had introduced the issue with a recent update to the iPhone's iOS software, indicating that a decision made by Apple in the software update led to the connectivity problem [94872].
Capability (Incompetence/Accidental) development_incompetence (a) The software failure incident related to development incompetence is evident in the article. O2 customer Jim Buckley mentioned that O2 had told him Apple had introduced the issue with a recent update to the iPhone's iOS software. This indicates that the software issue was likely caused by a lack of professional competence in the development process, leading to the network connectivity problems experienced by iPhone XR users on O2's network [94872]. (b) The software failure incident does not seem to be related to accidental factors based on the information provided in the article.
Duration temporary (a) The software failure incident related to the iPhone XR on O2's network was temporary. O2 mentioned that turning the phone off and on again temporarily fixed the problem, indicating that the issue was not permanent [94872]. Additionally, Apple stated that the issue causing intermittent network connectivity for some O2 customers would be resolved in an upcoming software release, further suggesting that the problem was not permanent [94872].
Behaviour omission, value, other (a) crash: The software failure incident in the article is not described as a crash where the system loses state and does not perform any of its intended functions [94872]. (b) omission: The software failure incident involves the omission of performing intended functions at instances, such as customers being unable to make and receive calls or send and receive texts, and struggling to get a reliable 4G internet connection [94872]. (c) timing: The software failure incident is not related to timing issues where the system performs its intended functions correctly but too late or too early [94872]. (d) value: The software failure incident is related to the system performing its intended functions incorrectly, such as the intermittent network connectivity issue affecting some O2 customers using iPhone XR [94872]. (e) byzantine: The software failure incident is not described as a byzantine failure where the system behaves erroneously with inconsistent responses and interactions [94872]. (f) other: The other behavior observed in the software failure incident is the system issue being introduced with a recent update to the iPhone's iOS software, causing network problems for O2 customers using iPhone XR [94872].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property, delay, theoretical_consequence (a) unknown (b) unknown (c) unknown (d) Property: The software failure incident impacted people's material goods as some O2 customers using iPhone XR experienced issues such as completely losing signal, being unable to make and receive calls or send and receive texts, and struggling to get a reliable 4G internet connection [94872]. (e) Delay: People had to postpone activities as a result of the software failure incident. For example, one customer had to resort to buying a second-hand iPhone 7 for £180 due to the network issue affecting his iPhone XR [94872]. (f) unknown (g) unknown (h) Theoretical_consequence: There were potential consequences discussed regarding the software failure incident. For instance, O2 and Apple were working on resolving the intermittent network connectivity issue affecting some customers using iPhone XR, and a fix was planned in an upcoming software release [94872]. (i) unknown
Domain information (a) The software failure incident reported in the article is related to the information industry, specifically affecting the functionality of the iPhone XR on O2's network, causing issues with making calls, sending texts, and accessing the internet [94872].

Sources

Back to List