UCCaaS Application Availability Sample Clauses

UCCaaS Application Availability. Application Availability is the amount of time the Platform is operating properly within the Customer instance across the Verizon data center(s) within a given month. A UCCaaS application is deemed “Available” if i) no Outage alarm events have occurred in the Verizon’s Network O perations Center (“NOC ”) affecting Customer within a region (U.S., EMEA, or Asia-Pacific) which resulted in a Trouble Ticket being opened, or ii) no Trouble Ticket related to Outages has been opened by Customer or by Verizon on behalf of Customer. Verizon provides standard UCCaaS reports including application availability on a monthly basis through the Verizon Enterprise Center portal; however such availability reports are for reference only and will not be used to measure UCCaaS service levels.
View SourceView Similar (3)
UCCaaS Application Availability. Availability is measured end-to-end and calculated as a percentage of the total reporting interval time that the UCCaaS for Government: SLED Edition service is operationally available to the Customer. 3.1.1 Calculation. Availability is computed by: Availability = ▇▇ (▇▇) - ▇▇▇ (▇▇) ▇ ▇▇▇ RI = Reporting interval HR = Hours COT = Cumulative Outage Time Calculation: Availability is the percentage of time that any individual UCCaaS application is available (i.e., not experiencing an Outage) within a given billing month as based upon recorded Outage time in associated Trouble Ticket(s).
View Source

Related to UCCaaS Application Availability

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • 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.

  • Product Availability Under no circumstances shall Company be responsible to Representative or anyone else for its failure to fill accepted orders, or for its delay in filling accepted orders, when such failure or delay is due to strike, accident, labor trouble, acts of nature, freight embargo, war, civil disturbance, vendor problems or any cause beyond Company's reasonable control.

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.