Uptime Commitment Sample Clauses

Uptime Commitment. CareerAmerica, LLC will use commercially reasonable efforts to ensure that the Ocelot Service is available 24 hours a day, 7 days a week, with a monthly uptime goal of 99%. As used herein, “Ocelot Uptime” is calculated by taking the total number of minutes in a calendar month less the number of minutes of Ocelot Downtime in the calendar month, divided by the total number of minutes in the calendar month. As used herein, “Ocelot Downtime” means if Ocelot Content and player are not being distributed or the Ocelot server is down, provided, however, that the following events will not be included as Ocelot Downtime: (a) causes beyond CareerAmerica LLC's reasonable control, and (b) scheduled maintenance on the Ocelot Service (“Scheduled Maintenance”) up to 8 hours per calendar month (the “Maintenance Limit”); all Scheduled Maintenance shall either be conducted (i) between the hours of 12:00 AM (ET) and 6:00 AM (ET) or (ii) at any time after supplying Client with 3 days advance notice (the “Maintenance Windows”). Any Schedule Maintenance conducted in excess of the Maintenance Limit or outside of the Maintenance Windows shall be included in the calculation of Ocelot Downtime. Client will promptly notify CareerAmerica, LLC of any failure to receive Ocelot Content, whereupon CareerAmerica, LLC will evaluate the report in order to determine whether or not such failure qualifies as Ocelot Downtime.
AutoNDA by SimpleDocs
Uptime Commitment. Bazaarvoice will deliver 99.9% uptime of the Bazaarvoice platform (the “Uptime Commitment”). The uptime is calculated as follows: (total minutes in any calendar month – total minutes of unavailability) divided by (the total minutes in same calendar month). Downtime during the weekly maintenance window does not count as a period of unavailability. The weekly maintenance window will not exceed two hours per week and will be scheduled during minimal traffic times.
Uptime Commitment a. Availability. The Service will be made available to Client and its Licensed Users twenty-four hours a day, seven days a week less the period during which the Service are not available due to one or more of the following events (collectively, the “Excusable Downtime”):
Uptime Commitment. 7.1 The Provider shall use reasonable endeavours to ensure that the Platform is available 99.9% of the time during each calendar month, subject to Paragraph 7.
Uptime Commitment. Castlight warrants to Customer that each month Uptime shall constitute at least 99.9% of Available Time for the Castlight Service (“Service Level Warranty”). If Castlight breaches the Service Level Warranty (as confirmed by the Monitoring Software), Castlight will issue a credit against the next invoice payable by Customer (and if no further invoices are due, Castlight will pay Customer the amount of the credit within thirty days of the end of this First Addendum). Such credit will be equal to five percent (5%) of Customer’s monthly Service Fee.
Uptime Commitment. 6.1 Quadrotech shall use reasonable endeavours to ensure that the Platform is avail- able the majority of the time during each calendar month, subject to Paragraph 8.
Uptime Commitment. RDSI shall provide Remote Customers access to the Software twenty-four (24) hours a day, seven (7) days per week in accordance with the following Uptime Commitment. Remote Customers shall be able to access the Software at least ninety-eight percent (98%) of the scheduled available time, determined on an annual basis, excluding downtime caused by telecommunication companies or other network service providers, Software defects, Customers, natural and man-made disasters or other force majeure events, and any other causes beyond the immediate control of RDSI (the “Uptime Commitment”). In the event that RDSI cannot or will not maintain its Uptime Commitment, NCHI will provide to RDSI a written notice of default specifying in detail the Uptime Commitment failures. If RDSI cannot substantially correct such default within ninety (90) days after receipt of notice, then NCHI shall have the right to contract with additional resellers for the license of the Software. RDSI will perform any scheduled maintenance outside of normal business hours.
AutoNDA by SimpleDocs
Uptime Commitment. The Uptime Percentage for the Service will be ninety-nine and five-tenths percent (99.5%) (the “Uptime Commitment”). Subject to the exclusions described in below, “Uptime Percentage” is calculated by subtracting from 100% the percentage of 1-minute periods during any annual billing cycle in which Agency’s selected Service(s) are unavailable out of the total number of minutes in that billing cycle. “Unavailable” and “Unavailability” mean that, in any 1-minute period, all connection requests received by Agency failed to process (each a “Failed Connection”); provided, however, that no Failed Connection will be counted as a part of more than one such 1-minute period (i.e. a Failed Connection will not be counted for the period 12:00:00-12:00:59 and the period 12:00:30-12:01:29). The Yearly Uptime Percentage will be measured based on the industry standard monitoring tools.
Uptime Commitment. BizLibrary will use commercially reasonable efforts to ensure that the Services will be available at least 99% of the time, as measured by calendar month, subject to the exclusions set forth below and also excluding scheduled downtime and any time necessary to implement any updates, upgrades or other modifications to the Services (“Uptime Commitment”). BizLibrary will use commercially reasonable efforts to minimize the effect of such maintenance on the Services.
Uptime Commitment. WhyzeHR shall be available at least 99% of the time over 12 months rolling period from maintenance start date. Uptime Measurement Scheduled Uptime = (Total Time (24/7)) – (Scheduled Maintenance Windows) % Availability = (Scheduled Uptime – Unplanned Downtime) / Scheduled Uptime Unplanned downtime is defined as the time when the fault is reported to Whyze to the time the application services are restored. Planned downtime refers to scheduled maintenance activities causing application service outages and should not be a factor in measuring service availability. Whyze deploys multiple servers and some of them act as the backup servers should the main servers fail. It shall not constitute a Downtime as long as the application services are accessible by the Customer, even though some of the servers may have failed.
Time is Money Join Law Insider Premium to draft better contracts faster.