Observed topology
AS48011 DigiTurunc Turunc Smart Bilgisayar Teknoloji Ve Dis Ticaret Limited Sirketi
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48011: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 580 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 548 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 397 |
| AS49127 | Asimo Networks B.V. | Hosting | IPv4 IPv6 | 381 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 336 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 237 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 129 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 84 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 45 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 20 |
Transit
Downstream networks
Networks for which AS48011 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59441 | NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.) | Hosting | IPv4 | 645 |
| AS212552 | BitCommand LLC | Unclassified | IPv4 IPv6 | 338 |
| AS57497 | Faraso Samaneh Pasargad Ltd. | Unclassified | IPv4 | 197 |
| AS202269 | BitCommand LLC | Unclassified | IPv4 | 52 |
| AS201999 | Fanavari Serverpars Argham Gostar Company Ltd. | Unclassified | IPv4 | 29 |
| AS197946 | Amnpardaz Soft Corporation | Unclassified | IPv4 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48011 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49127 | Asimo Networks B.V. | Hosting | IPv4 IPv6 | 916 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 829 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 748 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 659 |
| AS59441 | NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.) | Hosting | IPv4 | 645 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 400 |
| AS212552 | BitCommand LLC | Unclassified | IPv4 IPv6 | 338 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 237 |
| AS57497 | Faraso Samaneh Pasargad Ltd. | Unclassified | IPv4 | 197 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 187 |
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.