asn.dev

Observed topology

AS47952 ICTBULUT ICT BULUT BILISIM A.S.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47952: 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
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv41,389
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv61,290
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4 IPv6405
AS15924Vodafone Net Iletisim Hizmetler ASUnclassifiedIPv4 IPv6363
AS202660"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv464
AS29049Delta Telecom LtdResidentialIPv460

Transit

Downstream networks

inferred

Networks for which AS47952 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 AS47952 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv41,389
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv61,290
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4 IPv6405
AS15924Vodafone Net Iletisim Hizmetler ASUnclassifiedIPv4 IPv6363
AS202660"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv464
AS29049Delta Telecom LtdResidentialIPv460

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.