asn.dev

Observed topology

AS58273 B4RN-AS

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS58273: 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
AS6461Zayo BandwidthTransitIPv4 IPv61,262
AS6939Hurricane Electric LLCTransitIPv4 IPv6679
AS3356Level 3 Parent, LLCTransitIPv4 IPv6247
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6128
AS50304Blix Solutions ASUnclassifiedIPv484
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv661
AS48185team.blue NVUnclassifiedIPv4 IPv661
AS174Cogent Communications, LLCTransitIPv4 IPv649
AS24482SG.GSHostingIPv4 IPv646
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv643

All 25 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213513Computle LimitedUnclassifiedIPv48

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,268
AS6939Hurricane Electric LLCTransitIPv4 IPv6679
AS3356Level 3 Parent, LLCTransitIPv4 IPv6249
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6128
AS50304Blix Solutions ASUnclassifiedIPv484
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv661
AS48185team.blue NVUnclassifiedIPv4 IPv661
AS174Cogent Communications, LLCTransitIPv4 IPv649
AS24482SG.GSHostingIPv4 IPv646
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv643

All 26 adjacent →

Provenance

Where this comes from

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