Peering Policy

Peering with AS13445

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.

Why peer with Cisco?

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

Peering information:

• ASN: 13445
• AS-SET: AS-WEBEX
• Recommended max prefixes: 100
• MD5: optional
• Peering contact: peering@webex.com
• NOC email: noc@webex.com
• SOC phone (24x7): +1 855-722-7227
  
  
• Ashburn, Equinix IPv4: 206.223.115.132
• Ashburn, Equinix IPv6: 2001:504:0:2:0:1:3445:1
• San Jose, Equinix IPv4: 206.223.116.132
• San Jose, Equinix IPv6: 2001:504:0:1:0:1:3445:1
• Miami, NOTA: 198.32.124.228
• New York, NYIIX IPv4: 198.32.160.37
• New York, NYIIX IPv6: 2001:504:1::A501:3445:1
• London, LINX IPv4: 195.66.225.110 (Brocade) and 195.66.227.110 (Extreme)
• London, LINX IPv6: 2001:7F8:4::3485:1 (Brocade) and 2001:7F8:4:1::3485:1 (Extreme)
• Frankfurt, DE-CIX IPv4: 80.81.194.105/22
• Frankfurt, DE-CIX IPv4: 80.81.194.105/22
• Frankfurt, DE-CIXIPv6: 2001:7f8::3485:0:1
• Paris, Equinix IPv4: 195.42.144.55
• Paris, Equinix IPv6: 2001:7F8:43::1:3445:1
• Amsterdam, AMS-IX IPv4: 195.69.144.75
• Amsterdam, AMS-IX IPv6: 2001:7F8:1::A501:3445:1
• Hong Kong, HKIX IPv4: 202.40.161.251

Peering requirements:

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.