Common use of Extraordinary Event Clause in Contracts

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 2087 contracts

Samples: Registry Agreement, Registry Agreement, Registry Agreement

AutoNDA by SimpleDocs

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twenty-four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight forty-eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 142 contracts

Samples: Registry Agreement, Registry Agreement, Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twenty‐four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight forty‐eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 18 contracts

Samples: Registry Agreement, Registry Agreement, Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four (24) 24 hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight (48) 48 hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 4 contracts

Samples: Registry Agreement, Registry Agreement, Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twenty-four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.forty-eight

Appears in 2 contracts

Samples: Registry Agreement, Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twenty-four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight forty-eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability. 3.3.

Appears in 2 contracts

Samples: Registry Agreement, Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twenty- four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight forty-eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 1 contract

Samples: Registry Agreement

AutoNDA by SimpleDocs

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twentyLfour (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight fortyLeight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 1 contract

Samples: Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable commerciallyreasonable efforts to restore the critical functions of the registry within twenty-­‐four twenty-four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight forty-eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 1 contract

Samples: Registry Agreement

Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four twentyMfour (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight fortyMeight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

Appears in 1 contract

Samples: Registry Agreement

Time is Money Join Law Insider Premium to draft better contracts faster.