Service Reliability Clause Samples
The Service Reliability clause defines the standards and expectations for the consistent and dependable performance of a service. It typically outlines metrics such as uptime percentages, response times, and procedures for addressing outages or disruptions. For example, it may require the service provider to maintain 99.9% availability and to notify clients promptly in the event of service interruptions. This clause ensures that clients can rely on the service for their business needs and provides recourse if reliability standards are not met, thereby minimizing operational risks and disruptions.
POPULAR SAMPLE Copied 4 times
Service Reliability. The parties will make commercially reasonable efforts to ensure that their respective services related to this Agreement are free from material defects, and are available 24 hours a day, 7 days a week to Users. Service Provider agrees to maintain the Service Provider Services according to the applicable restoral expectations set forth in the table below. For unplanned events, Sprint will assign a trouble severity code based on Sprint’s assessment of trouble at the point of trouble identification. Sprint will make adjustments to the trouble severity code based on event activities. Operational reviews between Sprint Technical Services and Service Provider will be conducted as needed. The following trouble severity table will be reviewed periodically by Sprint and Service Provider, and may be modified by mutual written agreement of the parties.
Service Reliability a. RapidDeploy shall use proactive and technically appropriate measures to provide an uptime of 99.99% for the RapidDeploy Platform Services for the measurement period and subject to exclusions outlined below in Section 2.
b. For unplanned downtime (an “Incident”), RapidDeploy will assign a trouble severity code and priority based on RapidDeploy’s assessment of the Event at the point of trouble identification. RapidDeploy will make adjustments to the trouble severity code based on how the Event proceeds.
Service Reliability. Rave shall provide an uptime of 99% for the Services, subject to scheduled updates and maintenance and to any downtime caused by the Client or by Third Party Service Providers. For unplanned downtime (an “Event”), Rave will assign a trouble severity code based on Rave’s assessment of the Event at the point of trouble identification. Rave will make adjustments to the trouble severity code based on how the Event proceeds.
Service Reliability. If the customer requires, they can measure the reliability of the service provided by the supplier. This will be achieved in two ways:
Service Reliability. 99.5%, excluding network problems (i) occurring between the customer's premise and the PSI Points-of-Presence, and (ii) occurring beyond the point where information exits the PSI backbone.
Service Reliability. We seek to have our Services available twenty-four (24) hours a day, seven (7) days a week, and to maintain all saved information. However, technical failures, acts of God and routine maintenance may render our Service unavailable at times, and/or may result in the loss of information. We shall not be liable to You or anyone else for any loss of information or for the non-availability of any Service, unless such loss of information or non-availability of a Service has resulted from our gross negligence.
Service Reliability. Subject to the terms and conditions of this Agreement, Scoir will use commercially reasonable efforts to make the Services generally available for use by Customer and its Invitees at any time, excluding planned downtime and any unavailability caused by circumstances beyond our reasonable control, including without limitation, acts of God, acts of government, floods, fires, earthquakes, civil unrest, acts of terror, strikes or other labor problems (other than those involving Scoir’s own employees), Internet service provider failures or delays, denial of service attacks, or any other force majeure event or factors. Scoir acknowledges that Customer may consider a failure to reasonably meet its service reliability commitments to be a material breach of this Agreement. Accordingly, and notwithstanding anything to the contrary in this Agreement, Customer's sole remedy for Scoir’s failure to reasonably meet its service reliability commitments shall be to terminate this Agreement for cause pursuant to Section 7.2.
Service Reliability. [This means the maximum number of service breaks that can be tolerated within an agreed period; it may be defined either as number of breaks in a timeframe, or as a Mean Time Between Failures (MTBF) or Mean Time Between Systems Incidents (MTBSI). Define what constitutes a ‘break’ and how these will be monitored and recorded.] As part of the quality of service, “The Service Provider” has designed the service to be resilient; enhancing in that way realibility. The commitments in this SLA are as follows: • No more than 2 (two) Failures in 12 (twelve) months, and • Mean Time Between Failures equal to or greater than 180 days. For the provision of the Service covered by this SLA, a Failure will be considered any Incident with Impact = Critical. See the referenced document ("The Client". Help Desk Service. List of Incidents and Services to Request.) to determine the Impact of an Incident.
Service Reliability. The maximum allowed number of incidents per month.
Service Reliability. While SBB strives to deliver as near to error free transmission and access Services as reasonably possible, it accepts no responsibility for failure of routes, connections, packet loss or router/server rejections that are beyond its control. SBB may from time to time purchase network access from national service providers to facilitate its own deployed backbone network. Because the information flow and network traffic changes dynamically, SBB may find it necessary to rebalance its own backbone to provide efficient routing capabilities. These changes may impact the routing paths that a Customer’s information uses to enter or exit SBB’s network. For these reasons, SBB does not guarantee specific network entrance or exit points. 5.