asn.dev

Observed topology

AS7768 TEKNET Nuh Ahmet Firat trading as TEKNET YAZILIM VE BILGISAYAR TEKNOLOJILERI

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS7768: 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.MobileIPv4 IPv6196
AS44901Belcloud LTDHostingIPv4183
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv4 IPv6159
AS4849S3 Company LtdHostingIPv4108
AS601443W Infra B.V.UnclassifiedIPv458
AS206375NETSPEED INTERNET A.S.ResidentialIPv421
AS37100SEACOM LimitedUnclassifiedIPv411
AS48185team.blue NVUnclassifiedIPv411
AS48362Stadtwerke FeldkirchResidentialIPv48
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv44

Transit

Downstream networks

inferred

Networks for which AS7768 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

All 19

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

ASNetworkTypeFamiliesPaths seen
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4 IPv6196
AS44901Belcloud LTDHostingIPv4183
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv4 IPv6159
AS4849S3 Company LtdHostingIPv4108
AS601443W Infra B.V.UnclassifiedIPv458
AS206375NETSPEED INTERNET A.S.ResidentialIPv421
AS37100SEACOM LimitedUnclassifiedIPv411
AS48185team.blue NVUnclassifiedIPv411
AS48362Stadtwerke FeldkirchResidentialIPv48
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv44

Provenance

Where this comes from

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