asn.dev

Observed topology

AS200334 netops-tr Alptekin Sunnetci

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200334: 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
AS34927iFog GmbHHostingIPv664
AS60707Kapteyan Bilisim Teknolojileri Sanayi ve Ticaret A.SUnclassifiedIPv460
AS8772Netassist International EOODUnclassifiedIPv67
AS202365Omer GOLGELIUnclassifiedIPv66
AS29632Netassist International EOODUnclassifiedIPv63
AS56662Marcin GondekUnclassifiedIPv61
AS401753BIXCE IncUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205381Mitues Global Teknolojiler Ltd. Sti.HostingIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv668
AS60707Kapteyan Bilisim Teknolojileri Sanayi ve Ticaret A.SUnclassifiedIPv460
AS205381Mitues Global Teknolojiler Ltd. Sti.HostingIPv412
AS202365Omer GOLGELIUnclassifiedIPv4 IPv610
AS8772Netassist International EOODUnclassifiedIPv67
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv63
AS56662Marcin GondekUnclassifiedIPv61

Provenance

Where this comes from

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