asn.dev

Observed topology

AS48822 UNIVERSUMNET-AS

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48822: 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
AS29076Citytelecom LLCHostingIPv4 IPv675
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv629
AS1299Arelion Sweden ABTransitIPv4 IPv623
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv615
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv63
AS9002RETN LimitedUnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51183Aktiv Computers Ltd.UnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29076Citytelecom LLCHostingIPv4 IPv6103
AS51183Aktiv Computers Ltd.UnclassifiedIPv462
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv641
AS1299Arelion Sweden ABTransitIPv4 IPv633
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv621
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv64
AS9002RETN LimitedUnclassifiedIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.