asn.dev

Observed topology

AS4258 ATG-4258

Unclassified ARIN

Upstreams 15 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 13
Upstream graph Who carries AS4258, and who carries them, drawn as a map up to the transit-free core. 8 exchanges Where AS4258 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS4258: 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.

ASNetworkTypeFamiliesPaths seen
AS6830Liberty Global Europe Holding B.V.ResidentialIPv496
AS6939Hurricane Electric LLCTransitIPv4 IPv637
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv621
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS9002RETN LimitedUnclassifiedIPv4 IPv613
AS22652Videotron LteeResidentialIPv46
AS24482SG.GSHostingIPv4 IPv64
AS293ESnetUnclassifiedIPv43
AS3130RGnet OUUnclassifiedIPv43
AS7575Australian Academic and Research Network (AARNet)EducationIPv43

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11608Accretive NetworksHostingIPv4 IPv6906
AS395487Accretive NetworksHostingIPv450

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS11608Accretive NetworksHostingIPv4 IPv6906
AS6939Hurricane Electric LLCTransitIPv4 IPv6271
AS6830Liberty Global Europe Holding B.V.ResidentialIPv4173
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6157
AS22652Videotron LteeResidentialIPv4 IPv6101
AS9002RETN LimitedUnclassifiedIPv4 IPv680
AS24482SG.GSHostingIPv4 IPv652
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv651
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv651
AS3130RGnet OUUnclassifiedIPv450

All 19 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.