asn.dev

Observed topology

AS48108 VIRTUALDC

Hosting RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48108: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6487
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv662
AS50509Transroute Telecom LTDUnclassifiedIPv645
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv639
AS24482SG.GSHostingIPv4 IPv613
AS9002RETN LimitedUnclassifiedIPv45
AS37721Virtual-Technologies-Solutions-SAResidentialIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43581ZTV CORP LLCUnclassifiedIPv4 IPv6971
AS213220Delta LtdUnclassifiedIPv6740
AS208626ServTech LTDHostingIPv4 IPv6532
AS42972JSC DPD RUSUnclassifiedIPv457

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv62,986
AS213220Delta LtdUnclassifiedIPv4 IPv61,485
AS43581ZTV CORP LLCUnclassifiedIPv4 IPv6971
AS208626ServTech LTDHostingIPv4 IPv6532
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv6360
AS50509Transroute Telecom LTDUnclassifiedIPv6175
AS24482SG.GSHostingIPv4 IPv674
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv663
AS42972JSC DPD RUSUnclassifiedIPv457
AS9002RETN LimitedUnclassifiedIPv427

All 11 adjacent →

Provenance

Where this comes from

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