Severity 3 Incident definition

Severity 3 Incident means an Event that: (a) has minimal current impact on Client, and (b) causes a malfunction of a non- essential RapidDeploy Service feature. Minor business impact - individual users affected only. Business Hours 1 business day N/A

Split View

AI-Powered Contracts

Draft, Review & Redline at the Speed of AI

Get StartedBook a Demo

Severity 3 Incident means a Security Incident that encompasses activity on a network or server that is not directly actionable. Discovery and vulnerability scanning, information gathering scripts, and other reconnaissance probes are grouped into this category;

Severity 3 Incident means an incident that has, or in the reasonable opinion of Telstra is likely to have, a noticeable impairment to the provision of the Consumer VMC Website to Telstra BigPond Customers or the business of Telstra.

Examples of Severity 3 Incident in a sentence

• For any Severity 3 Incident occurring during a given calendar month, Global shall pay, in the form of a credit against fees owing by Mercury for such month, $***** per incident in excess of ***** Severity 3 Incidents in such month (i.e., penalties start with incident ***** in any month) up to a maximum of $***** for such month.

• The Service Provider shall report progress on any Severity 3 Incident each Working Day until the Incident is resolved.

• Example Scenarios:  Significant number of users not receiving email  Interruptions to non-critical management functions 2 hours 8 hours 5 business days S3 A Severity 3 Incident arises when the Software is unable to function properly in a production environment due to a failure of the Software to conform to the Documentation and/or Specifications where such failure does not materially impact Company’s business operation.

• Severity 3 Incident - Medium Customer impacting incident requiring a managed restoration where business impact is minimal despite network, product or service unavailability or degradation.

• JUNYO’s response time to a Severity 3 Incident will be within 1 Business Day.

• The Incident will then be logged in ▇▇▇▇▇▇▇▇’▇ Incident tracking system and the Incident will be classified as a Severity 1, Severity 2, or Severity 3 Incident.

More Definitions of Severity 3 Incident

Severity 3 Incident represents a lower impact problem that involves a ***or ***of ***, or some other problem involving ***. CoreLogic can continue *** operations and a workaround solution may exist which allows for continued *** operations.

Severity 3 Incident is an Error or potential Error that has a minor restriction on the development, deployment, or operational use of the Hosted Service, resulting in the ability to continue to develop, deploy, or use the Hosted Service as required or intended but also resulting in minor inconvenience. JUNYO’s response time to a Severity 3 Incident will be within 1 Business Day.

Severity 3 Incident is a minor issue which causes important Element Service features to be unavailable (but a workaround is available), or less significant Element Service features to be unavailable, but Customer’s production use is continuing.