Availability Events
Availability Events Sample Clauses
Related to Availability Events
RDDS availability Refers to the ability of all the RDDS services for the TLD, to respond to queries from an Internet user with appropriate data from the relevant Registry System. If 51% or more of the RDDS testing probes see any of the RDDS services as unavailable during a given time, the RDDS will be considered unavailable.
Availability of Services CBT agrees not to discontinue or refuse to provide any service provided or required hereunder other than in accordance with the terms of this Agreement, or unless required by the Commission.
Availability of Service We will use reasonable efforts to make the Service available for your use on a continuous basis. The Service may be unavailable for short periods of time for regular or emergency system maintenance. We will endeavor to have our scheduled maintenance occur during non-peak hours. In addition, accessibility to the Service may be interrupted because of conditions beyond our control, including outages in Internet, cellular or other communications availability. We will use diligent efforts to re-establish the Services as promptly as possible. We do not promise the Service will always be available for your use. We may elect to discontinue this Service at any time. If we choose to discontinue the Service, we will provide you with reasonable notice in advance of that fact. We reserve the right at all times to take actions to protect our systems and information, including denial of access to users of the Service.
Availability Control Personal Data will be protected against accidental or unauthorized destruction or loss. Measures: • SAP employs regular backup processes to provide restoration of business-critical systems as and when necessary. • SAP uses uninterrupted power supplies (for example: UPS, batteries, generators, etc.) to protect power availability to the Data Centers. • SAP has defined business contingency plans for business-critical processes and may offer disaster recovery strategies for business critical Services as further set out in the Documentation or incorporated into the Order Form for the relevant Cloud Service. • Emergency processes and systems are regularly tested.
Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):
Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:
Fund Availability Financial obligations of the University payable after the current Fiscal Year are contingent upon funds for that purpose being appropriated, budgeted, and otherwise made available.
Funds Availability For determining the availability of your deposits, every day is a business day except Saturdays, Sundays, federal holidays and legal banking holidays in the State of Utah.
Non-Availability of Funds Every payment obligation of the State under this Charter is conditioned upon the availability of funds continuing to be appropriated or allocated for the payment of such obligations. If funds are not allocated and available for the continuance of this Charter, the Commission may terminate this Charter at the end of the period for which funds are available. No liability shall accrue to the Commission, nor the State, or any of its subdivisions, departments or divisions, in the event this provision is exercised, and neither the Commission nor the State shall be obligated or liable for any future payments or for any damages as a result of termination under this paragraph.
High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-‐level redundancy, end-‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.
