Observed topology

AS196874 TELENET-RSM TeleneT San Marino

Unclassified RIPE

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

Upstream graph Who carries AS196874, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS196874 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS196874: 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.

AS	Network	Type	Families	Paths seen
AS12874	Fastweb SpA	Residential	IPv4	118
AS212841	A.A.S.S. Azienda Autonoma di Stato per i Servizi Pubblici	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS213557	Underscore S.r.l.	Unclassified	IPv4	60
AS215511	Underscore S.r.l.	Unclassified	IPv4	60
AS34468	S.S.I.S.	Unclassified	IPv4	52
AS212841	A.A.S.S. Azienda Autonoma di Stato per i Servizi Pubblici	Unclassified	IPv4	27

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12874	Fastweb SpA	Residential	IPv4	317
AS213557	Underscore S.r.l.	Unclassified	IPv4	60
AS215511	Underscore S.r.l.	Unclassified	IPv4	60
AS34468	S.S.I.S.	Unclassified	IPv4	52
AS212841	A.A.S.S. Azienda Autonoma di Stato per i Servizi Pubblici	Unclassified	IPv4	29

Provenance

Where this comes from

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