asn.dev

Observed topology

AS207983 CODIT-GW Codit Teknoloji Tic. Ltd. Sti.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207983: 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
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4186
AS24961WIIT AGHostingIPv4 IPv692
AS206119Veganet Teknolojileri ve Hizmetleri LTD STIUnclassifiedIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208095Internetten Teknoloji Bilisim Sanayi ve Ticaret Ltd. Sti.UnclassifiedIPv4185
AS58209Murat Terzioglu trading as PREBITSUnclassifiedIPv4 IPv6151
AS218790BASE9 BILISIM TEKNOLOJILERI TICARET ASUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4371
AS24961WIIT AGHostingIPv4 IPv6243
AS208095Internetten Teknoloji Bilisim Sanayi ve Ticaret Ltd. Sti.UnclassifiedIPv4185
AS58209Murat Terzioglu trading as PREBITSUnclassifiedIPv4 IPv6151
AS206119Veganet Teknolojileri ve Hizmetleri LTD STIUnclassifiedIPv4120
AS218790BASE9 BILISIM TEKNOLOJILERI TICARET ASUnclassifiedIPv460

Provenance

Where this comes from

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