Uptime/Downtime Sample Clauses

Uptime/Downtime. Uptime shall mean any time that the System is not down ("Uptime"). A down System means that a patient cannot be treated due to an actual malfunction of the System and that the System is immediately available for an Accuray service engineer to work on it ("Downtime").
Uptime/Downtime. The Inktomi Search Engine running the Site Search Services will have a minimum uptime operation of [*]% (downtime of [*]%) over monthly windows with a goal of *Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. [*]% uptime. Downtime shall mean any one minute interval in which the Inktomi Search Engine is unable to process search requests.
Uptime/Downtime. For any given month during the Term, the GO Network-Wrapped Pages hosted by Content Partner will have a minimum monthly uptime operation of (***) excluding permitted maintenance downtime, provided that such scheduled downtime does not occur at peak traffic times.
Uptime/Downtime. The Inktomi Search Engine running the Premium Content Search Services will have a minimum uptime operation of [*] over monthly windows. Downtime shall mean any one minute interval in which the Inktomi Search Engine is unable to process search requests.
Uptime/Downtime. The Inktomi Search Engine running the Premium Content Search Services will have a minimum uptime operation of [*] over monthly windows. Downtime shall mean any one minute interval in which the Inktomi Search Engine is unable to process search requests. Production Schedule ------------------- Powerize will begin work on constructing the Interface and identifying the Premium Content URL List and the Powerize Database, and Inktomi will begin work on tuning its Search Engine to provide the services set forth herein promptly upon execution of this Agreement. Both parties will use commercially reasonable efforts so that the Premium Search Services are available to Powerize for use in the Site are available within 90 days following the Effective Date.

Related to Uptime/Downtime

  • Downtime Each of Zero Hash and ZHLS uses commercially reasonable efforts to provide the Services in a reliable and secure manner. From time to time, interruptions, errors, delays, or other deficiencies in providing the Services may occur due to a variety of factors, some of which are outside of Zero Hash’s and/or ZHLS’ control, and some which may require or result in scheduled maintenance or unscheduled downtime of the Services (collectively, “Downtime”). You understand and acknowledge that part or all of the Services may be unavailable during any such period of Downtime, and you acknowledge that Zero Hash and ZHLS are not liable or responsible to you for any inconvenience or losses to you as a result of Downtime. Following Downtime, you further understand and acknowledge that the prevailing market prices of cryptocurrency may differ significantly from the prices prior to such Downtime.

  • Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate ▇▇▇▇▇’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Service Outages (a) Service Outages Due to Power Failure or Disruption. 911 Dialing does not function in the event of a power failure or disruption. If there is an interruption in the power supply, the Service, including 911 Dialing, will not function until power is restored. Following a power failure or disruption, you may need to reset or reconfigure the Device prior to utilizing the Service, including 911 Dialing. (b) Service Outages Due to Internet Outage or Suspension or Termination of Broadband Service or ISP Service. Service outages or suspensions or terminations of service by your broadband provider or ISP will prevent all Service, including 911 Dialing, from functioning. (c) Service Outage Due to Suspension or Termination of Your Citi-Tel Account. Service outages due to suspension or termination of your account will prevent all Service, including 911 Dialing, from functioning. (d) Service Outages Due to ISP or Broadband Provider Blocking of Ports or Other Acts. Your ISP or broadband provider or other third party may intentionally or inadvertently block the ports over which the Service is provided or otherwise impede the usage of the Service. In that event, provided that you alert us to this situation, we will attempt to work with you to resolve the issue. During the period that the ports are being blocked or your Service is impeded, and unless and until the blocking or impediment is removed or the blocking or impediment is otherwise resolved, your Service, including the 911 Dialing feature, may not function. You acknowledge that Citi-Tel is not responsible for the blocking of ports by your ISP or broadband provider or any other impediment to your usage of the Service, and any loss of service, including 911 Dialing, that may result. In the event you lose service as a result of blocking of ports or any other impediment to your usage of the Service, you will continue to be responsible for payment of the Service charges unless and until you terminate the Service in accordance with this Agreement.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.