The Webex backbone as a network destination

See also

Sources

1. 1
   Webex accepts at most 100 routes from a customer over an Edge Connect BGP session.

   Webex Edge Connect · Webex Edge Connect article, requirements: BGP parameters · Checked 2026-10-14
2. 2
   Over Edge Connect, Webex accepts customer prefixes no longer than /29.

   Webex Edge Connect · Webex Edge Connect article, requirements: BGP parameters · Checked 2026-10-14
3. 3
   Over Edge Connect, Webex advertises prefixes no longer than /24.

   Webex Edge Connect · Webex Edge Connect article, requirements: BGP parameters · Checked 2026-10-14
4. 4
   Cisco recommends that customers allow 500 routes from Webex on the Edge Connect BGP session, because the number of advertised routes may change over time.

   Webex Edge Connect · Webex Edge Connect article, requirements: BGP parameters · Checked 2026-10-14
5. 5
   The Webex public BGP autonomous system number used for Edge Connect peering is 13445.

   Webex Edge Connect · Webex Edge Connect article, requirements: BGP parameters · Checked 2026-10-14
6. 6
   BFD is enabled by default on the Webex side of Edge Connect links at 300 ms x 3, for both Meetings/Calling links and Dedicated Instance links.

   Webex Edge Connect · Webex Edge Connect article, requirements: BGP parameters (BFD) · Checked 2026-10-14
7. 7
   Cisco stated in 2018 that 24x7 operations teams around the world monitor the Webex backbone, with extensive telemetry on its links.

   The Webex Backbone: Because Every Millisecond Counts · Cisco blog 'The Webex Backbone: Because Every Millisecond Counts', paragraph on operations · Checked 2026-10-14
8. 8
   In 2018 Cisco said the Webex backbone carried more than 6 billion minutes a month.

   The Webex Backbone: Because Every Millisecond Counts · Cisco blog 'The Webex Backbone: Because Every Millisecond Counts', paragraph on scale · Checked 2026-10-14
9. 9
   Cisco described the Webex backbone in 2018 as using hot-potato routing to take packets off the public Internet as soon as possible and carry them on Cisco's private, media-optimised backbone.

   The Webex Backbone: Because Every Millisecond Counts · Cisco blog 'The Webex Backbone: Because Every Millisecond Counts', paragraph on hot potato routing · Checked 2026-10-14
10. 10
    Cisco stated in 2018 that media is encrypted in transit between Webex cloud locations.

    The Webex Backbone: Because Every Millisecond Counts · Cisco blog 'The Webex Backbone: Because Every Millisecond Counts', paragraph on security · Checked 2026-10-14
11. 11
    Cisco stated in 2018 that the Webex backbone connects all its data centers with redundant paths and that some locations use dual 100G links.

    The Webex Backbone: Because Every Millisecond Counts · Cisco blog 'The Webex Backbone: Because Every Millisecond Counts', paragraph on redundant paths · Checked 2026-10-14
12. 12
    On February 25, 2026, Cisco added 150.253.214.128/25 and 150.253.220.0/24 to the Webex Calling APAC ranges in the Edge Connect article.

    Webex Edge Connect · Webex Edge Connect article, revision history entry dated February 25, 2026 · Checked 2026-10-14
13. 13
    Cisco lists the Webex Calling data centers as Chicago, Dallas, Vancouver and Toronto; Amsterdam, Frankfurt, Manchester and London; Melbourne, Sydney, Osaka, Tokyo, Chennai and Mumbai; and Jeddah and Riyadh.

    Data Center locations for Webex Calling · Data Center locations for Webex Calling, Table 1 · Checked 2026-10-14
14. 14
    Cisco states that filtering Webex Calling traffic by IP address alone with only a firewall is not supported, because some address pools are dynamic; domains and URLs must also be allowed.

    Port Reference Information for Webex Calling · Port Reference Information for Webex Calling, Webex Calling traffic through proxies and firewalls · Checked 2026-10-14
15. 15
    Cisco lists additional Webex Calling media points of presence in Los Angeles, New Jersey, Dallas, Singapore, Seoul, Sao Paulo, Cape Town and the United Arab Emirates.

    Data Center locations for Webex Calling · Data Center locations for Webex Calling, Table 2 (Additional Webex Calling Media PoP) · Checked 2026-10-14
16. 16
    Cisco does not endorse filtering a subset of Webex Calling IP addresses by geographic region or cloud provider, saying it can cause severe degradation to calling.

    Port Reference Information for Webex Calling · Port Reference Information for Webex Calling, IP Subnets for Webex Calling services · Checked 2026-10-14
17. 17
    Webex tags Calling routes advertised over Edge Connect with origin communities 13445:20000 (AMER), 13445:20010 (EMEA), 13445:20020 (ANZ) and 13445:20060 (APAC).

    Webex Edge Connect · Webex Edge Connect article, BGP communities: origin tags (Calling) · Checked 2026-10-14
18. 18
    Cisco states that Webex Calling uses its own data centers plus third-party hosting providers and business partners to deliver service globally.

    Data Center locations for Webex Calling · Data Center locations for Webex Calling, introductory paragraph · Checked 2026-10-14
19. 19
    Tagging a customer route with community 13445:677 limits its propagation inside the Webex backbone to the local theater; without it the route is reachable globally.

    Webex Edge Connect · Webex Edge Connect article, BGP communities: route propagation scope · Checked 2026-10-14
20. 20
    For Dedicated Instance, Edge Connect uses primary/secondary location pairs: Singapore/Tokyo (APJC), Melbourne/Sydney (AUS), Frankfurt/Amsterdam (EU), Los Angeles/Ashburn (AMER) and London/Manchester (UK).

    Webex Edge Connect · Webex Edge Connect article, data centers: Dedicated Instance · Checked 2026-10-14
21. 21
    For Dedicated Instance Edge Connect, a second link is included, selecting redundancy is mandatory, and the request portal requires two connections.

    Webex Edge Connect · Webex Edge Connect article, redundancy section and Edge Connect Request Portal steps · Checked 2026-10-14
22. 22
    Webex Edge Connect is a private network peering connection that bypasses the public Internet and connects the customer network directly to the Webex backbone.

    Webex Edge Connect · Webex Edge Connect article, opening overview paragraph · Checked 2026-10-14
23. 23
    Edge Connect uses a cloud exchange provider, Equinix or Megaport, to link the customer's routing edge to the edge routers of the Webex backbone.

    Webex Edge Connect · Webex Edge Connect article, opening overview paragraph · Checked 2026-10-14
24. 24
    The Edge Connect article names Webex Meetings, Webex Calling and Webex Contact Center Enterprise data centers as reachable over the Edge Connect peering.

    Webex Edge Connect · Webex Edge Connect article, opening overview paragraph · Checked 2026-10-14
25. 25
    The two Calling APAC ranges added to the Edge Connect lists in February 2026 (150.253.214.128/25 and 150.253.220.0/24) fall inside 150.253.128.0/17, which Cisco already lists as a Webex media and Calling subnet, so firewall rules built from the port reference should already allow them.inferred

    Port Reference Information for Webex Calling · Port Reference Information for Webex Calling, IP Subnets for Webex Calling services (list 1), compared with the Edge Connect article revision entry dated February 25, 2026 · Checked 2026-10-14
26. 26
    The Edge Connect on-ramp list and the Webex Calling data center list are different sets (for example, San Jose and Ashburn are on-ramps but not listed Calling data centers, and Vancouver and Chennai are Calling data centers but not on-ramps), so Calling traffic entering at an on-ramp must cross the Webex backbone to reach the data center hosting the service.inferred

    Webex Edge Connect · Webex Edge Connect article, data centers section, compared with Data Center locations for Webex Calling, Table 1 · Checked 2026-10-14
27. 27
    AS13445 has public peering and facility presence in Jeddah and Riyadh according to PeeringDB, yet Edge Connect does not support Saudi Arabia data centers, so public peering presence in a metro does not imply that Edge Connect is available there.inferred

    WebEx Communications (AS13445) · PeeringDB net 1517, exchange and facility tables (SAIX, center3), compared with the Edge Connect article data centers note · Checked 2026-10-14
28. 28
    Cisco's Webex data center article lists Internet Points of Presence (IPOP) in Los Angeles, San Jose, New York and Texas (USA), Amsterdam, and Sydney and Melbourne, and lists none for the Middle East and Africa.

    Where are the Webex Data Centers and iPOP Locations? · Webex Data Centers and IPOP article, IPOP (Internet Points of Presence) table · Checked 2026-10-14
29. 29
    Customers can tag routes with communities 13445:200 through 13445:900 to set the Webex-side local preference of an Edge Connect link to 200 through 900; 13445:900 is most preferred and an untagged route is least preferred.

    Webex Edge Connect · Webex Edge Connect article, BGP communities: Link Priority · Checked 2026-10-14
30. 30
    Cisco does not support or recommend filtering Webex media IP addresses to a particular geographic region, because doing so can seriously degrade meetings.

    Network Requirements for Webex Services · Network Requirements for Webex Services, IP subnets for Webex media services section · Checked 2026-10-14
31. 31
    Webex apps and devices test reachability and round-trip time to media nodes at startup, on network change and periodically, and the Webex cloud picks a media server by transport protocol (UDP preferred), round-trip time and server availability.

    Network Requirements for Webex Services · Network Requirements for Webex Services, IP subnets for Webex media services section · Checked 2026-10-14
32. 32
    The Webex media subnet list in the network requirements article includes 150.253.128.0/17.

    Network Requirements for Webex Services · Network Requirements for Webex Services, IP subnets for Webex media services (IPv4 list) · Checked 2026-10-14
33. 33
    Webex tags Meetings routes advertised over Edge Connect with origin communities 13445:10000 (AMER), 13445:10010 (EMEA) and 13445:10020 (APAC).

    Webex Edge Connect · Webex Edge Connect article, BGP communities: origin tags (Meetings) · Checked 2026-10-14
34. 34
    The latest revision of the Edge Connect article (September 17, 2026) removed some Webex Meetings ranges from the by-theater lists.

    Webex Edge Connect · Webex Edge Connect article, revision history entry dated September 17, 2026 · Checked 2026-10-14
35. 35
    Megaport's guide states that, once a request is submitted, Webex configures its edge routers with backbone connectivity to the different Webex data centers.

    Connecting to Cisco Webex Edge Connect · Megaport 'Connecting to Cisco Webex Edge Connect', overview of the Cisco-side steps · Checked 2026-10-14
36. 36
    Megaport lists the Webex Edge Connect locations it serves as Singapore SG1, Sydney SY1, Melbourne ME1, Tokyo TY2, Amsterdam AM1, London Telehouse North, Frankfurt FR5, Ashburn DC4, Chicago CH4, Dallas DA1, San Jose SV1 and New York Digital Realty NYC2.

    Connecting to Cisco Webex Edge Connect · Megaport 'Connecting to Cisco Webex Edge Connect', Webex locations list · Checked 2026-10-14
37. 37
    Megaport's guide says an Edge Connect order needs an account on the Webex Edge Connect portal at https://edgeconnect.webex.com.

    Connecting to Cisco Webex Edge Connect · Megaport 'Connecting to Cisco Webex Edge Connect', Prerequisites · Checked 2026-10-14
38. 38
    In the Megaport portal, a VXC to Webex takes a rate limit in Mbps starting at 1 Mbps and a VLAN ID from 2 to 4093, or untagged.

    Connecting to Cisco Webex Edge Connect · Megaport 'Connecting to Cisco Webex Edge Connect', VXC details step · Checked 2026-10-14
39. 39
    AS-PATH prepending does not work with a private customer ASN on Edge Connect because Webex strips the private ASN after ingress; Cisco directs such customers to Link Priority Communities instead.

    Webex Edge Connect · Webex Edge Connect article, traffic engineering section · Checked 2026-10-14
40. 40
    Edge Connect does not accept private prefix advertisements such as RFC1918, so advertised customer space must be public, provider-independent space.

    Webex Edge Connect · Webex Edge Connect article, requirements: IP addressing · Checked 2026-10-14
41. 41
    The Edge Connect article lists the international on-ramp data centers as Amsterdam, London, Frankfurt, Singapore, Sydney and Tokyo.

    Webex Edge Connect · Webex Edge Connect article, data centers: International · Checked 2026-10-14
42. 42
    The Edge Connect article lists the North American on-ramp data centers as Ashburn, Chicago, Dallas, New York, San Jose, Montreal and Toronto.

    Webex Edge Connect · Webex Edge Connect article, data centers: North America · Checked 2026-10-14
43. 43
    Edge Connect is ordered in Cisco Commerce Workspace by adding SKU A-FLEX-3, selecting the Edge Connect add-on, then choosing locations (Americas/EMEAR and/or APJ) and bandwidth.

    Webex Edge Connect · Webex Edge Connect article, Ordering section (added June 9, 2025) · Checked 2026-10-14
44. 44
    The customer supplies the Edge Connect peering link addresses for both sides, and they must be public addresses on a /30 or /31.

    Webex Edge Connect · Webex Edge Connect article, requirements: IP addressing · Checked 2026-10-14
45. 45
    PeeringDB lists AS13445 at 15 private interconnection facilities, mostly Equinix sites (Ashburn, San Jose, Dallas, Amsterdam, London LD8, Singapore, Sydney, Toronto, Tokyo) plus CoreSite LA1, Digital Realty Chicago and New York, center3 Jeddah and Riyadh, and Sify Mumbai.

    WebEx Communications (AS13445) · PeeringDB net 1517, Interconnection Facilities table · Checked 2026-10-14
46. 46
    PeeringDB lists AS13445 at 20 public exchange points, including AMS-IX, DE-CIX Frankfurt, DE-CIX Mumbai, LINX LON1 and LON2, NYIIX, BBIX Tokyo, JPNAP Tokyo, MegaIX Sydney, NL-ix, eight Equinix IX metros and SAIX Jeddah and Riyadh.

    WebEx Communications (AS13445) · PeeringDB net 1517, Public Peering Exchange Points table · Checked 2026-10-14
47. 47
    PeeringDB records the IRR as-set for AS13445 as AS-WEBEX.

    WebEx Communications (AS13445) · PeeringDB net 1517, IRR as-set/route-set field · Checked 2026-10-14
48. 48
    PeeringDB classifies AS13445 as a Content network with a Mostly Outbound traffic ratio, Global scope and undisclosed traffic levels.

    WebEx Communications (AS13445) · PeeringDB net 1517, Network Type, Traffic Ratios, Geographic Scope and Traffic Levels fields · Checked 2026-10-14
49. 49
    PeeringDB records 500 IPv4 prefixes and 50 IPv6 prefixes for AS13445.

    WebEx Communications (AS13445) · PeeringDB net 1517, IPv4 Prefixes and IPv6 Prefixes fields · Checked 2026-10-14
50. 50
    PeeringDB marks AS13445 as a route-server peer at 11 exchanges and as BFD-capable at 3 (Equinix Melbourne, SAIX Jeddah and SAIX Riyadh).

    WebEx Communications (AS13445) · PeeringDB net 1517, Public Peering Exchange Points table, RS Peer and BFD columns · Checked 2026-10-14
51. 51
    PeeringDB records AS13445 (WebEx Communications) with a Selective general peering policy and with multiple locations, a ratio requirement and a contract all marked not required.

    WebEx Communications (AS13445) · PeeringDB net 1517, Peering Policy Information fields · Checked 2026-10-14
52. 52
    The Webex Calling port reference lists the Edge Connect private network peering connection to the Webex backbone among the Webex Suite services whose IP subnets, domains and URLs must be allowed through the firewall.

    Port Reference Information for Webex Calling · Port Reference Information for Webex Calling, Firewall configuration section · Checked 2026-10-14
53. 53
    Cisco recommends accepting all Webex routes of /24 or shorter over Edge Connect. The per-theater prefix lists in the article are informational only, and firewall rules should come from the Webex port and network reference articles.

    Webex Edge Connect · Webex Edge Connect article, IP ranges (By Theater) note · Checked 2026-10-14
54. 54
    Cisco's product page describes Webex Edge Connect as a managed, QoS-enabled peering connection from the customer premises to Webex.

    Cisco Webex Edge Connect · Cisco Webex Edge Connect product page, introduction · Checked 2026-10-14
55. 55
    Cisco takes up to 10 business days to provision an Edge Connect request.

    Webex Edge Connect · Webex Edge Connect article, ordering / Edge Connect Request Portal · Checked 2026-10-14
56. 56
    For Meetings and Calling, Edge Connect offers an optional discounted second connection to a different Webex data center in a geographically distinct region.

    Webex Edge Connect · Webex Edge Connect article, redundancy section · Checked 2026-10-14
57. 57
    Cisco advises connecting to the Edge Connect on-ramp data centers in the customer's own region, and advises large customers with national or international networks to peer with Webex regionally.

    Webex Edge Connect · Webex Edge Connect article, data centers introduction · Checked 2026-10-14
58. 58
    The Edge Connect article states that Saudi Arabia data centers are not supported for Edge Connect.

    Webex Edge Connect · Webex Edge Connect article, data centers note · Checked 2026-10-14
59. 59
    After Cisco configures the Webex side, the customer creates an Ethernet virtual circuit to Webex on the exchange provider's portal using a service key that Cisco sends from csg-peering@cisco.com.

    Webex Edge Connect · Webex Edge Connect article, connection steps · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). The Webex backbone as a network destination. WarmTransfer. https://warmtransfer.net/knowledge/webex-backbone

@misc{warmtransfer-webex-backbone,
  title  = {The Webex backbone as a network destination},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-backbone},
  note   = {Verified 2026-10-14}
}