Observed topology
AS8449 AS8449-ELCAT
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8449: 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 AS8449 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12764 | AKNET Ltd. | Unclassified | IPv4 | 3,782 |
| AS50223 | Alfa Telecom CJSC | Unclassified | IPv4 | 2,340 |
| AS12997 | OJSC Kyrgyztelecom | Unclassified | IPv4 IPv6 | 2,210 |
| AS41750 | Mega-Line Ltd. | Residential | IPv4 IPv6 | 1,562 |
| AS42837 | Extra Line LLC | Unclassified | IPv4 | 1,220 |
| AS59684 | Hoster kg, Ltd. | Unclassified | IPv4 | 606 |
| AS207369 | Skynet Telecom, LLC | Residential | IPv4 IPv6 | 526 |
| AS42581 | Inform Communications Ltd. | Unclassified | IPv4 | 384 |
| AS47237 | NUR Telecom LLC | Unclassified | IPv4 IPv6 | 328 |
| AS39214 | Kyrgys Russian Slavic University named after First President of Russia B.N. Yeltsin | Unclassified | IPv4 | 256 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8449 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35168 | TNS-Plus LLP | Unclassified | IPv4 IPv6 | 11,328 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 7,690 |
| AS12764 | AKNET Ltd. | Unclassified | IPv4 | 4,497 |
| AS12997 | OJSC Kyrgyztelecom | Unclassified | IPv4 IPv6 | 2,404 |
| AS50223 | Alfa Telecom CJSC | Unclassified | IPv4 | 2,340 |
| AS41750 | Mega-Line Ltd. | Residential | IPv4 IPv6 | 1,683 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,554 |
| AS42837 | Extra Line LLC | Unclassified | IPv4 | 1,220 |
| AS47237 | NUR Telecom LLC | Unclassified | IPv4 IPv6 | 1,205 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 752 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.