Severe Problem Sample Clauses

Severe Problem. A Problem that persists for a period of [*] or more during Peak Hours and [*] or more during Non-Peak Hours.

Severe Problem. Any error, bug or malfunction that causes the Ask Jeeves Service to become inaccessible to Customer and its end-users, or that causes any feature of the Service to become continuously unavailable.

Severe Problem. Any error, bug, or malfunction that causes the Powerize Data Engine to become inaccessible to Inktomi and its Site end users, or that causes any feature of the Powerize Data Engine to become continuously unavailable.

Severe Problem. An error, bug, incompatibility or malfunction, which causes a Service not to operate substantially as designed, and/or renders the Results substantially unavailable to or substantially unusable by Yahoo! (and which lasts for [*] or more), including issues which cause more than [*]% of queries to exceed the Critical Threshold. Once a Moderate Problem has been outstanding for more than [*], either party may, using their judgment, upgrade the issue to a Severe Problem. For the purposes of clarity, in the event that an issue with the monitoring infrastructure falsely identifies a problem that does not in truth exist on a large scale, that false positive will not be considered a Severe Problem (though the issue with the monitoring infrastructure should be addressed in its own right).

Severe Problem. An error, bug, incompatibility, malfunction, corruption, data error or other issue which causes a Service and/or Additional Service not to operate substantially as designed, and/or renders the Returned Data substantially unavailable to or substantially unusable by Yahoo! (and which lasts for [*] or more), including issues which cause more than [*]% of Calls in one or more of the America, AsiaPac or EMEA regions to exceed the Critical Threshold; sudden unanticipated changes in core business metric (RPS, coverage, depth, CRR, yield, revenue, etc.); ads not serving or updating for more than [*] PDAs or from any PDAs in the top [*]% of spend; or a significant degradation of performance reported by more than [*] PDAs. For the purposes of clarity, both parties agree that automated systems to detect Severe Problems do not and may not ever exist. Once a Moderate Problem has been outstanding for more than [*], either party may, using their judgment, upgrade the issue to a Severe Problem. For the purposes of clarity, in the event that an issue with the monitoring infrastructure falsely identifies a problem that does not in truth exist on a large scale, that false [*] Indicates that certain information in this exhibit has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to omitted portions. positive will not be considered a Severe Problem (though the issue with the monitoring infrastructure should be addressed in its own right).

Severe Problem. An error, bug, incompatibility or malfunction, which causes the Services not to operate substantially as designed, and/or renders the Results or Conduit Content substantially unavailable to or substantially unusable by End Users. Once a Moderate Problem has been outstanding for more than four hours, either party may, using their judgment, upgrade the issue to a Severe Problem.

Severe Problem. Any error, bug, or malfunction of the e-lingo Service that causes the e-lingo Translation Engine to become inaccessible to Customer and its Site end users, or that causes any feature of the e-lingo Translation Engine to become continuously unavailable.