The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Brief Study of Peering Policies study.  Clauses were categorized and put into rough categories for comparison.

Here are the clauses we roughly categorized as requirements for providing a path for escalating outages

----------

Escalation Path

Both parties shall provide an escalation path for resolving network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours. – InterNap

The Network Operations Center should also have an escalation path to senior level engineers for resolving issues in a timely manner. – NAC

# tw telecom peers must agree to actively respond to all technical emergencies as soon as possible. Issues that are not an emergency or performance impacting should be responded to within 2 business days. A history of sub-standard responses may result in de-peering. – TW Telecom

Both parties shall provide an escalation path for resolving network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours. – nLayer

# Peers must provide the means by which to escalate and resolve network emergencies. – Mzima

Upon identification of a customer-impacting peering event (outage), technicians will make themselves available for immediate troubleshooting and restoration of the peering session. – Highwinds

Prior to the peering session being established, a copy of Network's escalation procedures and contact information will be exchanged. – Highwinds