asn.dev

Observed topology

AS48972 BETTER-BE

Hosting RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS48972: 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
AS20847Previder B.V.HostingIPv4 IPv666
AS20562Broadband Hosting B.V.HostingIPv4 IPv653
AS24785Broadband Hosting B.V.HostingIPv4 IPv647
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS204092Association GRIFONUnclassifiedIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200934Defzone B.V.UnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS200934Defzone B.V.UnclassifiedIPv4 IPv693
AS20847Previder B.V.HostingIPv4 IPv684
AS20562Broadband Hosting B.V.HostingIPv4 IPv678
AS24785Broadband Hosting B.V.HostingIPv4 IPv666
AS6939Hurricane Electric LLCTransitIPv4 IPv655
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS204092Association GRIFONUnclassifiedIPv4 IPv67
AS29632Netassist International EOODUnclassifiedIPv66

Provenance

Where this comes from

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