asn.dev

Observed topology

AS48371 WESTLAN-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48371: 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
AS25308CityLanCom LTDUnclassifiedIPv433
AS47379SITS LtdUnclassifiedIPv423
AS44020Modern Solutions LTDUnclassifiedIPv47
AS24482SG.GSHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30854Velnet Telecom, LLCUnclassifiedIPv4372
AS51017STOLICA LLCUnclassifiedIPv465
AS62366Stolica Telecom Ltd.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS30854Velnet Telecom, LLCUnclassifiedIPv4372
AS44020Modern Solutions LTDUnclassifiedIPv4260
AS25308CityLanCom LTDUnclassifiedIPv4159
AS47379SITS LtdUnclassifiedIPv469
AS51017STOLICA LLCUnclassifiedIPv465
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS62366Stolica Telecom Ltd.UnclassifiedIPv42

Provenance

Where this comes from

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