Observed topology
AS43994 SMARTNET-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS43994: 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.
Transit
Downstream networks
Networks for which AS43994 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS205431 | HostLab LLC | Unclassified | IPv4 | 128 |
| AS214461 | Cloudpard LLC | Unclassified | IPv4 | 106 |
| AS48502 | ForteBank JSC. | Unclassified | IPv4 | 63 |
| AS208602 | Solidcore Eurasia LLP | Unclassified | IPv4 | 63 |
| AS202995 | Zhetisu-M-Telecom LLP | Unclassified | IPv4 | 62 |
| AS216202 | Subsidiary VTB Bank JSC Kazakhstan | Unclassified | IPv4 | 61 |
| AS214789 | Nova Cloud LLP | Unclassified | IPv4 | 56 |
| AS213048 | Air Astana JSC | Unclassified | IPv4 | 44 |
| AS197487 | JSC Microfinance Organization KMF | Unclassified | IPv4 | 20 |
| AS203167 | FOODMASTER-TRADE COMPANY LLP | Unclassified | IPv4 | 12 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43994 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,390 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 IPv6 | 2,014 |
| AS41798 | JSC Transtelecom | Unclassified | IPv4 IPv6 | 609 |
| AS59583 | Network Kazakhstan LLC | Unclassified | IPv4 | 279 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 142 |
| AS205431 | HostLab LLC | Unclassified | IPv4 | 128 |
| AS44653 | JSC People's Savings Bank Kazakhstan | Unclassified | IPv4 | 124 |
| AS214461 | Cloudpard LLC | Unclassified | IPv4 | 106 |
| AS214789 | Nova Cloud LLP | Unclassified | IPv4 | 83 |
| AS48502 | ForteBank JSC. | Unclassified | IPv4 | 63 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.