Peering Policy

Cisco WebEx supports open, settlement-free Internet peering at public Internet exchanges, and operates a 24 x 7 Network Operations Center with immediate escalation paths to our Tactical Assistance Center and Senior Network Engineers.

Learn about our carrier-grade network, the Cisco WebEx Collaboration Cloud.

• Better cost. Avoid having to pay a third party ISP to carry WebEx traffic. 
• Better performance. Reduce latency and potential bottlenecks since traffic flows directly from your network to the WebEx network, without traversing third party networks over the public Internet.
• Better security. Eliminate the threat of third party interception since customer traffic never traverses the Internet.
• Better control. Pass routing information directly between your networks and WebEx by engineering traffic to have better priority and take preferred routes.
• Better resilience. Back up the direct peering connecting using standard Internet routing.

ASN: 13445
IRR: AS13445
Recommended max prefixes: 100
MD5: optional
Peering contact: peering@webex.com
NOC email: noc@webex.com
NOC phone (24x7): 650-691-7244

Ashburn, Equinix: 206.223.115.132
San Jose, Equinix: 206.223.116.132
London, LINX: 195.66.225.110 and/or 195.66.227.110
Tokyo, JPIX: TBD, coming Q3 2009

1. The peer must be located at an IX where Cisco maintains a
presence, or negotiate private peering.

2. The peer must operate an experienced 24 hours a day, 7 days a week
Network Operations Center with immediate escalation paths to Senior
Network Engineers, and provide email and contact numbers for
the NOC.

3. When notified of a peering or traffic issue(s), escalate immediately to a senior qualified engineer and provide timely resolution.

4. The peer shall report network maintenance issues that may affect our
BGP session and traffic exchanges.

5. The peer must NOT point any default route of last resort, add a static
route, or otherwise send traffic for a route not advertised over our BGP
session. We do not provide transit to other networks. All traffic sent to us
must have a specific destination IP address within any of the
WebEx prefixes we may advertise over BGP to you.

6. Email peering@webex.com, and include your contact information,
AS number, IP addresses at the peering points listed above, and
preferably a list of AS numbers / Prefixes you will be announcing to
us.

7. We reserve the right to immediately shutdown peering should any event
begin to detrimentally affect our network. Such events may include, BGP session flaps, route flaps, excessive routes, denial of service attacks or spam.

We reserve the right to modify this document at anytime.