Observed topology

AS398044 FIBERFED - Trinity Network Solutions

Residential ARIN NSP

Upstreams 7 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 1

Upstream graph Who carries AS398044, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS398044 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS398044: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	76
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	74
AS174	Cogent Communications, LLC	Transit	IPv4	72
AS20214	Comcast Cable Communications, LLC	Unclassified	IPv4	61
AS6939	Hurricane Electric LLC	Transit	IPv4	39
AS293	ESnet	Unclassified	IPv4	4
AS14907	Wikimedia Foundation Inc.	Hosting	IPv4	4

Transit

Downstream networks

inferred

Networks for which AS398044 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS398800	Town of Little Elm	Unclassified	IPv4	53
AS397761	CORSICANA ISD	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS398044 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	101
AS174	Cogent Communications, LLC	Transit	IPv4	83
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	83
AS20214	Comcast Cable Communications, LLC	Unclassified	IPv4	61
AS398800	Town of Little Elm	Unclassified	IPv4	53
AS6939	Hurricane Electric LLC	Transit	IPv4	47
AS293	ESnet	Unclassified	IPv4	5
AS14907	Wikimedia Foundation Inc.	Hosting	IPv4	5
AS397761	CORSICANA ISD	Unclassified	IPv4	2

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.