Observed topology

AS15806 ORG-IG30-RIPE

Residential RIPE Government

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15806: 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
AS207044	Enet Telecommunications Networks Limited	Residential	IPv4 IPv6	208
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	50
AS6830	Liberty Global Europe Holding B.V.	Residential	IPv4	4
AS9002	RETN Limited	Unclassified	IPv6	3
AS20562	Broadband Hosting B.V.	Hosting	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS24675	Irish Government	Unclassified	IPv4	210

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS207044	Enet Telecommunications Networks Limited	Residential	IPv4 IPv6	408
AS24675	Irish Government	Unclassified	IPv4	210
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	50
AS6830	Liberty Global Europe Holding B.V.	Residential	IPv4	9
AS20562	Broadband Hosting B.V.	Hosting	IPv4	8
AS9002	RETN Limited	Unclassified	IPv6	3

Provenance

Where this comes from

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