Observed topology

AS209275 NETMAX

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209275: 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
AS15924	Vodafone Net Iletisim Hizmetler AS	Unclassified	IPv4	300
AS6939	Hurricane Electric LLC	Transit	IPv4	26
AS25091	IP-Max SA	Unclassified	IPv4	2
AS208972	GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS48779	Bizim Bulut Bilgi ve Iletisim Hizmetleri San. ve Tic. A. S.	Unclassified	IPv4	118

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15924	Vodafone Net Iletisim Hizmetler AS	Unclassified	IPv4	392
AS48779	Bizim Bulut Bilgi ve Iletisim Hizmetleri San. ve Tic. A. S.	Unclassified	IPv4	118
AS6939	Hurricane Electric LLC	Transit	IPv4	50
AS208972	GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI	Unclassified	IPv4	4
AS25091	IP-Max SA	Unclassified	IPv4	2

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.