Observed topology
AS43727 KVANT-TELECOM JSC KVANT-TELEKOM
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS43727: 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,132 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 1,357 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 251 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 160 |
| AS47122 | CYBERFIRST LLC | Unclassified | IPv4 | 160 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 88 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 88 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 88 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 88 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 87 |
Transit
Downstream networks
Networks for which AS43727 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24689 | JSC Rosin.telekom | Residential | IPv4 | 5,237 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 IPv6 | 4,443 |
| AS44604 | JSC KVANT-TELEKOM | Unclassified | IPv4 | 1,565 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 | 1,436 |
| AS34550 | LLC Intercon | Unclassified | IPv4 | 782 |
| AS16323 | Informatsionniye Systemy i Technologii CJSC. | Unclassified | IPv4 | 628 |
| AS41575 | Intercity Ltd. | Unclassified | IPv4 | 613 |
| AS34602 | MEGASVYAZ LLC | Unclassified | IPv4 | 502 |
| AS41344 | Vist on-line LTD | Unclassified | IPv4 | 447 |
| AS13178 | LLC "Real-net" | Unclassified | IPv4 IPv6 | 404 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43727 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 40,303 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 IPv6 | 15,495 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 IPv6 | 15,040 |
| AS41798 | JSC Transtelecom | Unclassified | IPv4 | 5,946 |
| AS24689 | JSC Rosin.telekom | Residential | IPv4 | 5,237 |
| AS35168 | TNS-Plus LLP | Unclassified | IPv4 IPv6 | 4,442 |
| AS202365 | Omer GOLGELI | Unclassified | IPv4 | 3,339 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 2,397 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 2,302 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 2,045 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.