asn.dev

Observed topology

AS47524 AS-TURKSAT Turksat Uydu Haberlesme Kablo TV ve Isletme A.S.

Mobile RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47524: 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
AS15924Vodafone Net Iletisim Hizmetler ASUnclassifiedIPv4 IPv617,408
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv4 IPv615,014
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4 IPv614,798
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,304
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv6655
AS25091IP-Max SAUnclassifiedIPv4 IPv6134
AS6939Hurricane Electric LLCTransitIPv6133

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS15924Vodafone Net Iletisim Hizmetler ASUnclassifiedIPv4 IPv617,453
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv4 IPv615,151
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4 IPv614,884
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,304
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv6923
AS25091IP-Max SAUnclassifiedIPv4 IPv6134
AS6939Hurricane Electric LLCTransitIPv6133

Provenance

Where this comes from

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