asn.dev

Observed topology

AS198090 ASLIBRA LIBRA S.R.L.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198090: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6314
AS6939Hurricane Electric LLCTransitIPv4 IPv671
AS207594Connectivia S.r.lUnclassifiedIPv4 IPv646
AS8218Zayo Infrastructure France SAUnclassifiedIPv47
AS24482SG.GSHostingIPv47
AS31543myNet GmbHResidentialIPv47
AS59919Brainbox S.r.l.ResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198843LIBRA S.R.L.UnclassifiedIPv4122
AS208337TELEMANAPOLI S.R.L.UnclassifiedIPv478

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6438
AS198843LIBRA S.R.L.UnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv4 IPv6101
AS207594Connectivia S.r.lUnclassifiedIPv4 IPv681
AS208337TELEMANAPOLI S.R.L.UnclassifiedIPv478
AS8218Zayo Infrastructure France SAUnclassifiedIPv410
AS24482SG.GSHostingIPv410
AS59919Brainbox S.r.l.ResidentialIPv410
AS31543myNet GmbHResidentialIPv49

Provenance

Where this comes from

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