Cogent Communications network profile

Cogent Communications: the low-cost transit specialist

Cogent Communications is a US-listed internet-backbone and metro-fiber operator, founded in 1999 and headquartered in Washington, DC. From inception Cogent built a position as the aggressively priced commodity IP-transit provider in the wholesale market, contrasting with the higher-touch managed-service positioning of competitors such as Level 3 (now Lumen), NTT, and Telia. The strategy was simple: heavy capex on wholly owned long-haul fiber and metro fiber rings, dense direct on-net building connectivity, and a transit price list that consistently undercut peers by a significant margin per megabit.

The result over twenty years has been a global footprint covering most large European, North American, and selected Latin American and Asian markets, with thousands of on-net commercial buildings directly cabled to Cogent fiber. The customer base spans content companies, enterprise corporate networks, large web hosting providers, and downstream regional ISPs who buy Cogent transit to reach the wider internet. Cogent is not a residential consumer ISP. Cogent does not operate access networks to homes, and there is no Cogent retail subscriber identity to attach to a consumer IP.

AS174: a Tier 1 backbone with massive customer-cone attribution

Cogent's primary autonomous system is AS174, registered to Cogent Communications and operating as one of the widely recognized Tier 1 backbones — meaning Cogent reaches every routable IP on the public internet without paying for upstream transit, relying solely on settlement-free peering and its own customer cone. AS174 sits near the top of any pan-internet peer ranking by customer- cone size, by advertised IPv4 routes, and by transit-customer count. The CAIDA AS-rank consistently places AS174 in the top ten by several network-structure metrics.

The practical consequence for IP attribution is important. An IP geolocating to "Cogent" rarely identifies a Cogent-internal user. Far more commonly it identifies a downstream-customer network whose traffic happens to traverse AS174 transit or whose IP space is announced to the internet through Cogent BGP. Downstream customers include managed-hosting companies, regional VPS providers, smaller ISPs without their own full-table transit, and corporate enterprise networks. Treating "Cogent IP" as equivalent to "Cogent corporate behavior" misreads the customer- cone structure entirely.

Hostname conventions and the cogentco.com signature

Cogent-issued IP space carries a distinctive PTR convention. Backbone-router interfaces typically resolve to hostnames in the form te0-0-0-X.rcr12.lon01.atlas.cogentco.com or similar — a structured hostname that encodes the interface name, the router identifier, the city code, and the network platform on thecogentco.com domain. Theatlas.cogentco.com subdomain is specific to the long-haul atlas backbone, while metro and customer-edge equipment uses related but distinct subdomains.

For trace and attribution analysis the cogentco.com PTR signature is one of the cleanest backbone identifiers in any public-data set. A traceroute through AS174 will surface recognizable hop names with city codes, which is useful for diagnosing inter-city routing without private operator data. Customer-issued IP space announced through AS174 does not necessarily use cogentco.com PTRs — the customer manages its own reverse DNS, so PTRs on downstream-customer space typically reflect the customer's branding rather than Cogent's.

The Hurricane Electric IPv6 peering dispute

Cogent has been involved in several public peering disputes over the years, most famously with Hurricane Electric (HE, AS6939) over IPv6 interconnection. The two operators have historically declined to peer with each other directly over IPv6, citing disagreements about the terms of settlement-free peering between operators of differing customer-cone sizes. The practical result is that for the IPv6 routing graph, single-homed customers of AS174 and single-homed customers of AS6939 can have difficulty reaching each other directly, and third-party transit becomes necessary to bridge the gap.

The dispute has been an oft-cited example of internet-backbone politics and has implications for any IPv6-only network design. Some operators and content companies maintain transit relationships with both Cogent and Hurricane Electric specifically to avoid the cross-reachability problem on IPv6. From an attribution standpoint, an IPv6 traceroute showing one path via AS174 and a clearly independent IPv6 path via a different transit for the same destination can be a signal of IPv6-specific peering arrangements that work around the Cogent-HE gap.

Service model: transit, dark fiber, and on-net buildings

Cogent's revenue mix is concentrated in three product categories. The core transit business sells full-table BGP transit to wholesale customers at competitive per-megabit pricing. The metro and long-haul dark-fiber business sells unlit fiber strands to carriers, hyperscalers, and large enterprises that operate their own optical infrastructure. The on-net corporate-Ethernet business sells dedicated internet access circuits and point-to-point connectivity to enterprises in buildings where Cogent has direct fiber drops.

The on-net building footprint is one of the most distinctive aspects of Cogent's network. The company has cabled directly into thousands of commercial buildings across North America and Europe, providing an on-net dedicated-Ethernet service without needing to interconnect with local-loop incumbents. The on-net buildings list is published and is one of the standard inputs when comparing wholesale-access options for corporate offices in supported metro markets.

The Sprint wireline acquisition and the T-Mobile US transition

In 2023 Cogent completed the acquisition of the Sprint wireline business from T-Mobile US. The transaction transferred a substantial US long-haul fiber footprint and associated enterprise customers from T-Mobile to Cogent. T-Mobile US had inherited the Sprint wireline business in the 2020 Sprint merger but had no strategic use for it, while Cogent's transit-and- fiber model fits the asset profile directly. The integration is being executed over multiple years, with associated IP-space and customer transitions still in progress at the time of writing.

The implication for attribution is transitional. Some IP ranges historically registered to Sprint are migrating to Cogent ownership. RIPE and ARIN WHOIS records may lag the operational ownership by months, and IPs labeled "Sprint" or "Sprint Wireline" in legacy databases may already be operationally Cogent. For investigations needing accurate current ownership, ARIN reassignment records and Cogent's own customer portal are more reliable than third-party geolocation databases during this integration period.

IPv6 strategy and routing-table coverage

Cogent's IPv6 deployment is comprehensive in terms of customer reachability through AS174, with native IPv6 transit available to wholesale customers and IPv6 BGP coverage extending across most of its long-haul network. The unresolved peering dispute with Hurricane Electric remains the most-cited limitation. Customers needing guaranteed IPv6 reachability to AS6939-homed destinations typically architect multi-transit IPv6 to bridge that gap rather than relying on AS174 IPv6 alone.

For attribution work the implication is that an AS174 IPv6 path may have meaningfully different reachability characteristics from an AS174 IPv4 path to the same destination. This is unusual among major Tier 1 networks and is one of the specific operational details worth checking before accepting a Cogent path as a viable single-transit option for a network. Pair an ASN lookup with a traceroute when checking real-world reachability rather than assuming uniform Cogent IPv4-and-IPv6 behavior.

Downstream-customer attribution and the "Cogent IP" problem

The single most common attribution error involving Cogent IPs is misreading downstream-customer identity as Cogent corporate identity. AS174 announces tens of thousands of downstream IPv4 prefixes belonging to customer networks ranging from large hosting companies to regional ISPs to corporate enterprises. The attribution chain in public-data tooling often surfaces the upstream network ("Cogent") as the most visible label, especially when the more-specific downstream registration is incomplete or stale.

For accurate identification of who actually operates a Cogent-tagged IP, the RIPE or ARIN WHOIS for the specific prefix (not the ASN) is the correct entry point. The prefix-level registration commonly identifies the downstream-customer entity, including hosting companies whose IP space is operationally independent from Cogent even though they buy transit through AS174. For abuse complaints, the correct workflow is to identify the prefix owner via WHOIS and contact them directly — sending the complaint to Cogent's network operations center will typically be redirected back to the downstream-customer's abuse contact.

Peering policy and the settlement-free disputes

Cogent's published peering policy historically has been stricter than peers of similar size, demanding ratio-and-traffic conditions for settlement-free interconnection that some prospective peers find unworkable. The strict policy has produced multiple operator-versus- operator standoffs over the years beyond the Hurricane Electric dispute, including periods of partial de-peering with Telia, Sprint, Level 3, and AT&T in which customers of one network could not directly reach customers of the other during the dispute window. These disputes typically resolve through commercial transit arrangements that bridge the temporary gap, but they have made Cogent a recurring example in internet-governance and net-neutrality discussions.

From an attribution standpoint the peering behavior matters because path differences between two destinations served by AS174 are not always explained by latency or capacity engineering but by the underlying peering economics. A traceroute that takes an unexpectedly long path between two well-connected operators may be following the consequence of a current or historical peering disagreement rather than a routing fault. This is a backbone-specific consideration that does not apply meaningfully to retail-ISP traceroutes.

Metro footprint and the on-net building strategy

Cogent's metro fiber footprint extends across most major North American and Western European business markets, with metro rings interconnecting dense clusters of commercial buildings. The metro strategy emphasizes direct fiber drops into tenant buildings rather than reliance on local-loop incumbents — Cogent customers in an on-net building can receive dedicated Ethernet service over Cogent's own fiber without involvement of the local incumbent telco. The economic model depends on amortizing the initial fiber-drop capex across many tenants in the same building, which is why Cogent's published on-net list emphasizes multi-tenant office towers in business districts rather than scattered single-tenant locations.

The implication for attribution is that some AS174 IPs map to specific recognizable commercial addresses with limited tenant-level granularity. An IP attributed to "Cogent" with a hostname encoding a metro market code (such as nyc, lon, or fra) typically reflects the metro hub the on-net circuit terminates at rather than the individual building or tenant. For corporate network identification on Cogent on-net circuits, the more useful signal is usually outbound DNS, TLS server names, or other application-layer fingerprints rather than IP geolocation alone.

Investigation pitfalls specific to Cogent IPs

Several attribution traps recur with AS174 IPs. First, downstream-customer space dominates AS174 attribution — the upstream "Cogent" label is correct at the BGP level but rarely identifies the operational owner of the prefix. Second, the Sprint Wireline transition is ongoing, so some IP space currently labeled Sprint in legacy databases is operationally Cogent. Third, the IPv4-versus-IPv6 reachability asymmetry from the Hurricane Electric peering dispute can produce path-divergence behavior that looks like a traffic-engineering anomaly but is actually structural.

Fourth, Cogent is not a consumer ISP — an IP attributed to "Cogent" is essentially never a residential subscriber, and analyses that assume consumer behavior on a Cogent IP are starting from a wrong premise. Fifth, the on-net building business produces dedicated Ethernet circuits to specific commercial addresses, and Cogent-tagged IPs sometimes map to recognizable corporate-tenant networks (large law firms, hedge funds, media companies) whose corporate behavior on the IP is independent of Cogent.

Quick reference summary

Cogent Communications is a Tier 1 internet backbone and on-net fiber operator, not a consumer ISP. AS174 is one of the largest IPv4 transit networks by customer cone and one of the recognizable Tier 1 operators globally. The cogentco.com PTR domain identifies Cogent-owned backbone-router interfaces but not downstream-customer space. The unresolved IPv6 peering dispute with Hurricane Electric remains a structural reachability constraint for IPv6 single-transit architectures using AS174 only.

The 2023 Sprint Wireline acquisition is still being integrated, with associated IP-space attribution changes that may not match published WHOIS during the transition. For per-IP attribution on Cogent-tagged ranges, pair an ASN lookup with a WHOIS lookup at the prefix level rather than the ASN level to identify the actual downstream operator behind a Cogent-announced IP before drawing operational conclusions.

The commodity-transit positioning means Cogent shows up disproportionately in low-margin hosting and bulk-traffic environments, including budget VPS providers and high-volume content delivery backends. Behavior originating from Cogent-tagged IPs in such environments reflects the downstream customer's operational profile rather than any property of Cogent itself, and Cogent's role is essentially providing the IP transit fabric that underlies the customer's own service. For abuse workflows in such environments the prefix-level WHOIS contact for the hosting customer is the productive entry point and the Cogent network operations center will redirect complaints accordingly. Treat AS174 as plumbing infrastructure rather than as a single coherent end-user operator when interpreting attribution at scale.