asn.dev

Observed topology

AS201205 ASN-FLUVIUS-SP Fluvius System Operator CV

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201205: 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 IPv672
AS174Cogent Communications, LLCTransitIPv438
AS6939Hurricane Electric LLCTransitIPv4 IPv630
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS45049Mohamed El BoudduntiResidentialIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS3303Swisscom (Schweiz) AGResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205561Fluvius System Operator CVUnclassifiedIPv4358

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS205561Fluvius System Operator CVUnclassifiedIPv4358
AS3356Level 3 Parent, LLCTransitIPv4 IPv6251
AS174Cogent Communications, LLCTransitIPv4159
AS35280F5 Networks SARLHostingIPv458
AS6939Hurricane Electric LLCTransitIPv4 IPv630
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS45049Mohamed El BoudduntiResidentialIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS3303Swisscom (Schweiz) AGResidentialIPv42

Provenance

Where this comes from

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