Observed topology

AS215492 Butler BUTLER CHAT I.K.E.

Hosting RIPE Content

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215492: 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
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	85
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	12
AS8280	SYNAPSECOM S.A. Provider of Telecommunications and Internet Services	Hosting	IPv4 IPv6	2
AS29632	Netassist International EOOD	Unclassified	IPv6	2
AS199081	Lancom Ltd.	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS215980	Eleftherios Touloumtzidis	Unclassified	IPv4 IPv6	177

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	234
AS215980	Eleftherios Touloumtzidis	Unclassified	IPv4 IPv6	177
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	30
AS29632	Netassist International EOOD	Unclassified	IPv6	8
AS8280	SYNAPSECOM S.A. Provider of Telecommunications and Internet Services	Hosting	IPv4 IPv6	6
AS199081	Lancom Ltd.	Unclassified	IPv4	2

Provenance

Where this comes from

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