Observed topology

AS215691 HOSTEALO

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.

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	522
AS205980	FZCO	Unclassified	IPv4 IPv6	93
AS49581	Ferdinand Zink trading as Tube-Hosting	Hosting	IPv4	60
AS19318	Interserver, Inc	Hosting	IPv4	58

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS200074	SN SOLUTIONS LLC	Hosting	IPv4	58
AS204134	Jose Socrates Reviejo Bermejo	Unclassified	IPv4	58
AS209809	ROCO HOST LTD	Unclassified	IPv4	58
AS210676	Appline Group LLC	Unclassified	IPv4	58
AS214639	TAKEHOST OU	Unclassified	IPv4	58
AS214693	Fusiora OU	Residential	IPv4	58
AS215693	Bruno Andres Sampedro Trujillo	Unclassified	IPv4	58

Adjacency

Adjacent networks

All 11

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	928
AS205980	FZCO	Unclassified	IPv4 IPv6	93
AS49581	Ferdinand Zink trading as Tube-Hosting	Hosting	IPv4	60
AS19318	Interserver, Inc	Hosting	IPv4	58
AS200074	SN SOLUTIONS LLC	Hosting	IPv4	58
AS204134	Jose Socrates Reviejo Bermejo	Unclassified	IPv4	58
AS209809	ROCO HOST LTD	Unclassified	IPv4	58
AS210676	Appline Group LLC	Unclassified	IPv4	58
AS214639	TAKEHOST OU	Unclassified	IPv4	58
AS214693	Fusiora OU	Residential	IPv4	58

All 11 adjacent →

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.