Laserfiche WebLink
20. data loss during a Routine or Emergency Maintenance event; <br />21. during any period when the Customer has released Service to Agile for maintenance or <br />rearrangement purposes (including, without limitation, during any Routine Network <br />Maintenance); <br />22. any period when the Customer elects not to release the Service for testing and/or repair <br />and continues to use it on an impaired basis; or <br />23. a breach by the Customer of its obligations under the Agreement or this Service <br />Attachment that is the cause of the Service Outage. <br />10.1 Service Credit - Service Outage <br />If a Service Outage occurs and the Customer submits a request in accordance with the <br />Remedies Section below, Agile will provide a credit (the "Outage Credit') for Service as <br />detailed in Appendix 2. <br />All Outage Credits will be credited to the Customer no later than the second subsequent <br />monthly invoice issued to the Customer for the affected Service. THE PROVISIONS OF THIS <br />SECTION SETS FORTH THE CUSTOMER'S SOLE AND EXCLUSIVE REMEDIES FOR <br />SERVICE OUTAGES EXCEPT AS EXPRESSLY PROVIDED ELSEWHERE IN THIS <br />SERVICE ATTACHMENT. <br />10.2 Remedies <br />Upon the Customer's request for an Outage Credit to Agile's help desk made within 30 <br />business days of the closing of the applicable trouble ticket, the Customer will be entitled to <br />Outage Credits as set forth herein. The maximum Outage Credit issued in anyone calendar <br />month may not exceed the applicable month's MRC for the affected Service Order. <br />An Outage will begin when the Customer opens a trouble ticket for the affected Service and <br />Agile acknowledges receipt of such trouble ticket and validates that the Service is affected by <br />an Outage, or when Agile becomes aware of Service Outages as a result of multiple <br />Customers being affected. Agile will not unreasonably withhold or delay such <br />acknowledgement and validation. <br />An Outage is concluded upon validation that the Outage has been cured and Agile closes out <br />the trouble ticket relating to such Outage. Agile will attempt to notify the Customer that Service <br />has been restored. <br />10.3 Excessive Outage <br />If a Customer's circuits experience either three or more Outages, or 24 aggregate hours of <br />Outages, in each instance in any 30 day period (an "Excessive Outage'), the Customer will <br />be entitled, in addition to the applicable Outage Credit due up to termination of the circuit, if <br />any, to terminate the affected circuits without charge or liability. <br />If during any 12 month period Excessive Outages have occurred with respect to 30% of the <br />highest number of all circuits deployed under this Service Attachment during the applicable <br />12 month period, then in addition to the remedies found elsewhere in this Service Attachment, <br />the Customer will have the option to terminate this Service Attachment on 30 days written <br />notice to Agile. The Customer must exercise this option within three months of the end of the <br />applicable 12 month period of Excessive Outages. For the avoidance of doubt, the remedy <br />set forth in this Section will only be exercisable by the Customer. <br />Agile Network Connect Service Attachment <br />10/1/19 Page 20 <br />