Common use of Incident Handling and Updates; Escalation Procedures; Planned Outages Clause in Contracts

Incident Handling and Updates; Escalation Procedures; Planned Outages. Company will be responsible for coordinating all incident isolation, testing and repair work for all Company Applications. Severity levels will be determined and communicated to Company by T-Mobile. During the incident * Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Confidential isolation and troubleshooting process, Company will communicate incident resolution progress with T-Mobile and escalate its problem resolution efforts based upon the times specified in the table below. Company will proactively inform T-Mobile when an issue or condition arises that may cause potential system anomalies and be a potential source for the creation of trouble tickets. Company will provide status updates as described below, which updates will include the following information: Start time of incident. Current status of repair. Description of the aspect(s) of the network components of all Networked Applications that is/are unavailable, with a detailed description of impact on Subscribers. Estimated time of repair. Also, in the event of a Severity Level 1 or 2 incident, Company will, at its own expense, post and maintain a “page down” “application down,” “feature down,” or similar status notice in a manner reasonably intended to inform all Subscribers of the status of the affected network components of all Networked Applications and, if possible, when the network components of all Networked Applications are likely to be fully restored. Severity Level and Incident Handling Notification Procedures Trouble Severity Code Description Restoral Period Status Update Intervals; Update Objectives Initial Response Time

Incident Handling and Updates; Escalation Procedures; Planned Outages. Company will be responsible for coordinating all incident isolation, testing and repair work for all Company Applications. Severity levels will be determined and communicated to Company by T-Mobile. During the incident * Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Confidential T-Mobile USA, Inc. isolation and troubleshooting process, Company will communicate incident resolution progress with T-Mobile and escalate its problem resolution efforts based upon the times specified in the table below. Company will proactively inform T-Mobile when an issue or condition arises that may cause potential system anomalies and be a potential source for the creation of trouble tickets. Company will provide status updates as described below, which updates will include the following information: Start time of incident. Current status of repair. Description of the aspect(s) of the network components of all Networked Applications that is/are unavailable, with a detailed description of impact on Subscribers. Estimated time of repair. Also, in the event of a Severity Level 1 or 2 incident, Company will, at its own expense, post and maintain a “page down” “application down,” “feature down,” or similar status notice in a manner reasonably intended to inform all Subscribers of the status of the affected network components of all Networked Applications and, if possible, when the network components of all Networked Applications are likely to be fully restored. Severity Level and Incident Handling Notification Procedures Trouble Severity Code Description Restoral Period Expectations Status Update Intervals; Update Objectives Initial Response Time