Observed topology
AS29049 Delta-Telecom-AS Delta Telecom Ltd
Residential RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS29049: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 966 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 861 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 612 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 570 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 543 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 424 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 393 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 369 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 352 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 305 |
Transit
Downstream networks
Networks for which AS29049 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215148 | Delta Telecom Ltd | Unclassified | IPv4 IPv6 | 6,534 |
| AS206977 | STATE SERVICE OF SPECIAL COMMUNICATION AND INFORMATION SECURITY OF THE REPUBLIC OF AZERBAIJAN | Unclassified | IPv4 | 1,413 |
| AS200446 | SELNET LLC | Unclassified | IPv4 | 1,342 |
| AS209489 | Azintex.com LLC | Unclassified | IPv4 | 1,342 |
| AS49345 | BEEONLINE OJSC | Unclassified | IPv4 | 1,220 |
| AS48830 | TransEuroCom LLC | Unclassified | IPv4 | 1,098 |
| AS201167 | Caspian Telecom LLC | Unclassified | IPv4 IPv6 | 1,014 |
| AS200729 | AzInTelecom LLC | Unclassified | IPv4 | 869 |
| AS39397 | Metronet LLC | Unclassified | IPv4 IPv6 | 803 |
| AS20661 | State Company of Electro Communications Turkmentelecom | Unclassified | IPv4 IPv6 | 539 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29049 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49666 | Telecommunication Infrastructure Company | Unclassified | IPv4 | 190,248 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 32,077 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 28,902 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 23,562 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 20,977 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 14,036 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 12,020 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 10,831 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 9,316 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 7,650 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.