asn.dev

Observed topology

AS15433 Tism Telecom Italia San Marino S.p.A

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15433: 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
AS174Cogent Communications, LLCTransitIPv42,370
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv41,185
AS6939Hurricane Electric LLCTransitIPv4790
AS3303Swisscom (Schweiz) AGResidentialIPv479
AS24482SG.GSHostingIPv479
AS31543myNet GmbHResidentialIPv479
AS59919Brainbox S.r.l.ResidentialIPv479

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201852Bluindaco S.R.L.UnclassifiedIPv4121
AS212841A.A.S.S. Azienda Autonoma di Stato per i Servizi PubbliciUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv42,430
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv41,221
AS6939Hurricane Electric LLCTransitIPv4810
AS201852Bluindaco S.R.L.UnclassifiedIPv4121
AS59919Brainbox S.r.l.ResidentialIPv482
AS3303Swisscom (Schweiz) AGResidentialIPv481
AS24482SG.GSHostingIPv481
AS31543myNet GmbHResidentialIPv481
AS212841A.A.S.S. Azienda Autonoma di Stato per i Servizi PubbliciUnclassifiedIPv44

Provenance

Where this comes from

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