Observed topology
AS29076 CITYTELECOM-AS Citytelecom LLC
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS29076: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 2,115 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 930 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 762 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 235 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 175 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 107 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 79 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 79 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 78 |
| AS34019 | Hivane Association | Unclassified | IPv4 | 78 |
Transit
Downstream networks
Networks for which AS29076 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS210079 | EuroByte LLC | Unclassified | IPv4 IPv6 | 3,797 |
| AS3175 | Citytelecom LLC | Hosting | IPv4 IPv6 | 2,667 |
| AS50289 | Limited Liability Company WELLCOM-L | Unclassified | IPv4 | 1,173 |
| AS49531 | "NetCom-R" LLC | Unclassified | IPv4 IPv6 | 963 |
| AS24663 | ZAO "COMPLAT-TELECOM" | Unclassified | IPv4 | 912 |
| AS41853 | Limited Liability Company NTCOM | Unclassified | IPv4 | 838 |
| AS41957 | Directive LLC | Unclassified | IPv4 | 810 |
| AS64419 | Ecotel, Ltd. | Unclassified | IPv4 | 731 |
| AS50867 | HOSTKEY B.V. | Hosting | IPv4 | 724 |
| AS60771 | Comiten Corp LLC | Unclassified | IPv4 | 531 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29076 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 12,045 |
| AS3175 | Citytelecom LLC | Hosting | IPv4 IPv6 | 7,039 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 4,812 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 4,534 |
| AS210079 | EuroByte LLC | Unclassified | IPv4 IPv6 | 3,797 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,515 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 2,267 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,247 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 1,957 |
| AS50289 | Limited Liability Company WELLCOM-L | Unclassified | IPv4 | 1,173 |
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.