asn.dev

Observed topology

AS215691 HOSTEALO AP INTERACTIVE SOLUTIONS SL

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215691: 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, LLCTransitIPv4531
AS205980FZCOUnclassifiedIPv4 IPv693
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv461
AS19318Interserver, IncHostingIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200074SN SOLUTIONS LLCHostingIPv459
AS204134Jose Socrates Reviejo BermejoUnclassifiedIPv459
AS209809ROCO HOST LTDUnclassifiedIPv459
AS210676Appline Group LLCUnclassifiedIPv459
AS214639TAKEHOST OUUnclassifiedIPv459
AS214693Fusiora OUResidentialIPv459
AS215693Bruno Andres Sampedro TrujilloUnclassifiedIPv459

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4944
AS205980FZCOUnclassifiedIPv4 IPv693
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv461
AS200074SN SOLUTIONS LLCHostingIPv459
AS204134Jose Socrates Reviejo BermejoUnclassifiedIPv459
AS209809ROCO HOST LTDUnclassifiedIPv459
AS210676Appline Group LLCUnclassifiedIPv459
AS214639TAKEHOST OUUnclassifiedIPv459
AS214693Fusiora OUResidentialIPv459
AS215693Bruno Andres Sampedro TrujilloUnclassifiedIPv459

Provenance

Where this comes from

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