Observed topology
AS25145 AS-TEKNOTEL Teknotel Telekomunikasyon Sanayi Ve Ticaret A.S.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS25145: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,708 |
| AS9121 | Turk Telekomunikasyon Anonim Sirketi | Mobile | IPv4 IPv6 | 2,250 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 715 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 371 |
| AS15924 | Vodafone Net Iletisim Hizmetler AS | Unclassified | IPv4 IPv6 | 177 |
| AS3223 | Voxility LLP | Hosting | IPv4 | 134 |
| AS34984 | Superonline Iletisim Hizmetleri A.S. | Mobile | IPv4 IPv6 | 75 |
| AS39582 | Vaultr Veri Merkezi Hizmetleri Anonim Sirketi | Hosting | IPv4 IPv6 | 64 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 57 |
Transit
Downstream networks
Networks for which AS25145 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51683 | Protahub Telekomunikasyon ve Bilisim Teknolojileri AS | Unclassified | IPv4 IPv6 | 349 |
| AS40934 | Fortinet Inc. | Unclassified | IPv4 | 102 |
| AS16740 | DOXX.NET CORPORATION | Unclassified | IPv4 IPv6 | 101 |
| AS43009 | Infobip Limited | Unclassified | IPv4 | 8 |
| AS202294 | Netlojik Bilgi Teknolojileri Sanayi ve Ticaret Limited Sirketi | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25145 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,959 |
| AS9121 | Turk Telekomunikasyon Anonim Sirketi | Mobile | IPv4 IPv6 | 2,317 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 773 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 408 |
| AS51683 | Protahub Telekomunikasyon ve Bilisim Teknolojileri AS | Unclassified | IPv4 IPv6 | 349 |
| AS15924 | Vodafone Net Iletisim Hizmetler AS | Unclassified | IPv4 IPv6 | 199 |
| AS34984 | Superonline Iletisim Hizmetleri A.S. | Mobile | IPv4 IPv6 | 138 |
| AS3223 | Voxility LLP | Hosting | IPv4 | 134 |
| AS39582 | Vaultr Veri Merkezi Hizmetleri Anonim Sirketi | Hosting | IPv4 IPv6 | 125 |
| AS40934 | Fortinet Inc. | Unclassified | IPv4 | 102 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.