asn.dev

Observed topology

AS215760 DISPAISY-AS Adam Grazioli

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS215760: 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
AS6939Hurricane Electric LLCTransitIPv6253
AS34927iFog GmbHHostingIPv664
AS44324MoeDove LLCResidentialIPv632
AS212895Johannes ErnstUnclassifiedIPv628
AS214757Jakub KrsaUnclassifiedIPv627
AS41720REVOLUTION PROVIDER SRLResidentialIPv620
AS11967Hop179 OUUnclassifiedIPv616
AS24482SG.GSHostingIPv614
AS401753BIXCE IncUnclassifiedIPv614
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204085Adam GrazioliUnclassifiedIPv6148
AS218789Soundvia LLCUnclassifiedIPv657
AS219079Eko Andri PrasetyoUnclassifiedIPv61

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6330
AS204085Adam GrazioliUnclassifiedIPv6148
AS34927iFog GmbHHostingIPv694
AS218789Soundvia LLCUnclassifiedIPv657
AS212895Johannes ErnstUnclassifiedIPv634
AS44324MoeDove LLCResidentialIPv632
AS11967Hop179 OUUnclassifiedIPv631
AS41720REVOLUTION PROVIDER SRLResidentialIPv629
AS214757Jakub KrsaUnclassifiedIPv627
AS58057Securebit AGUnclassifiedIPv622

Provenance

Where this comes from

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