# cogent Published articles for cogent. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Introducing the J2SW BGP Community Builder DevFeed: [Introducing the J2SW BGP Community Builder]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-29T18:30:21Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [networking](), [Routing (disambiguation)](), [configuration]() Tags: [aws-direct-connect](), [bgp](), [bgp-communities](), [builder](), [cisco](), [cogent](), [frrouting](), [hurricane-electric](), [juniper](), [mikrotik](), [network-engineering-resources](), [ntt](), [routing-policy]() ### AI overview The J2SW BGP Community Builder helps users select documented provider communities and routing actions, then generates scoped configuration fragments. It includes RFC well-known communities and policies from AWS Direct Connect, NTT DATA, Hurricane Electric, and Cogent Communications, with support for MikroTik RouterOS 7, Cisco IOS-XE, Juniper Junos, and FRRouting. ### Source excerpt The J2SW BGP Community Builder selects documented provider communities and generates scoped policy fragments for MikroTik, Cisco, Junos, and FRRouting. The post Introducing the J2SW BGP Community Builder appeared first on Justin Wilson (j2sw). ## Packets Down Range #41: New Cogent Route, The Hedge, GPC and Ritter Communications DevFeed: [Packets Down Range #41: New Cogent Route, The Hedge, GPC and Ritter Communications]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-23T03:13:40Z Content type: news Language: en Sources: [Justin Wilson (j2sw)]() Topics: [communications](), [Network](), [BGP](), [datacenter](), [Internet]() Tags: [2026](), [bgp](), [cogent](), [data-center](), [fd-ix](), [git](), [github](), [justin-wilson](), [monitoring](), [nbbc](), [network](), [news](), [packets-down-newsletter](), [packets-down-range](), [podcast](), [protocol]() ### AI overview Packets Down Range #41 is a networking news roundup covering ISP developments, fiber and data-center interconnection upgrades, Cogent's new East Coast fiber route, BGP monitoring with BMP, Claude's use in reviving a Digi console server, IPinfo activity logs, and related community news. ### Source excerpt Welcome to Packets Down Range #41. The post Packets Down Range #41: New Cogent Route, The Hedge, GPC and Ritter Communications appeared first on Justin Wilson (j2sw). ## Airtel-Tata Comm routing is cold potato in India? DevFeed: [Airtel-Tata Comm routing is cold potato in India?]() Original publisher: [Read original article]() Published: 2026-05-20T13:20:53Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [Routing (disambiguation)](), [networking](), [BGP]() Tags: [airtel](), [arelion](), [as1299](), [as174](), [as4755](), [as9498](), [bgp](), [cogent](), [india](), [routing](), [tata-comm]() ### AI overview An analysis of traceroutes between Airtel (AS9498) and Tata Comm (AS4755) in India suggests their routing tends toward cold-potato behavior. The article explains hot- and cold-potato routing, compares Arelion and Cogent traces, and examines possible interpretations of an Airtel-to-Tata Comm trace. ### Source excerpt Over the years, I have seen a number of traces between Airtel (AS9498) and Tata Comm (AS4755) in India, which strongly suggests that routing tends to be 'cold potato' between them. By default, routing between large backbones that interconnect across different locations is typically 'hot potato' - meaning traffic exits to other ASNs as close to the source as possible Hot potato routing is common Hot potato routing is quite common across large backbones. Let's analyse this concept by tracing between Arelion AS1299 and Cogent AS174 from their respective looking glasses. Trace Arelion AS1299 (Frankfurt) -> Cogent AS174 (San Francisco) - 66.250.250.146 (ism01.sfo01.atlas.cogentco.com): Router: ffm-b11 / Frankfurt (Equinix FR5, Kleyerstrasse) Command: traceroute ipv4 66.250.250.146 timeout 1 source Loopback0 Tracing the route to 66.250.250.146 1 * * * 2 be7948.ccr42.fra05.atlas.cogentco.com (154.54.72.126) 1 msec 1 msec be5484.ccr41.fra05.atlas.cogentco.com (130.117.1.1) 1 msec 3 be3343.ccr41.ams03.atlas.cogentco.com (154.54.62.142) 9 msec be2950.ccr42.ams03.atlas.cogentco.com (154.54.72.41) 9 msec be3343.ccr41.ams03.atlas.cogentco.com (154.54.62.142) 9 msec 4 be9036.ccr82.lon05.atlas.cogentco.com (154.54.72.185) 104 msec be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 104 msec 104 msec 5 port-channel8444.ccr92.lhr01.atlas.cogentco.com (154.54.72.182) 16 msec port-channel3464.ccr91.lhr01.atlas.cogentco.com (154.54.75.150) 17 msec 17 msec 6 be8668.ccr31.bos01.atlas.cogentco.com (154.54.167.29) 99 msec be3501.ccr42.jfk02.atlas.cogentco.com (154.54.95.101) 101 msec be8668.ccr31.bos01.atlas.cogentco.com (154.54.167.29) 104 msec 7 be8030.ccr22.alb02.atlas.cogentco.com (154.54.169.226) 104 msec port-channel2994.ccr92.cle04.atlas.cogentco.com (154.54.31.233) 99 msec be8029.ccr21.alb02.atlas.cogentco.com (154.54.169.222) 104 msec 8 be2718.ccr42.ord01.atlas.cogentco.com (154.54.7.129) 101 msec port-channel8023.ccr92.cle04.atlas.cogentco.com (154.54.169.197) 99 msec 99 msec 9