Observed topology
AS28910 INTAL-ASN
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS28910: 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 | 68 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 50 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 35 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 32 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 27 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 27 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 IPv6 | 27 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 20 |
| AS205103 | Telegraph42 Management GmbH | Unclassified | IPv4 IPv6 | 12 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 11 |
Transit
Downstream networks
Networks for which AS28910 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS55330 | AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK | Unclassified | IPv4 | 4,952 |
| AS49273 | COSCOM Liability Limited Company | Unclassified | IPv4 IPv6 | 4,358 |
| AS8449 | "ElCat" Ltd. | Unclassified | IPv4 IPv6 | 2,811 |
| AS8193 | "Uzbektelekom" Joint Stock Company | Residential | IPv4 IPv6 | 1,410 |
| AS12365 | JC LLC Sarkor-Telecom | Hosting | IPv4 IPv6 | 1,351 |
| AS34718 | "IST TELEKOM" JV LLC | Unclassified | IPv4 IPv6 | 1,311 |
| AS41202 | UNITEL LLC | Unclassified | IPv4 | 1,089 |
| AS31203 | Sharq Telekom CJSC | Unclassified | IPv4 | 1,041 |
| AS43060 | IPLUS LLC | Residential | IPv4 IPv6 | 817 |
| AS47139 | CJSC INDIGO TAJIKISTAN | Unclassified | IPv4 | 791 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28910 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS205103 | Telegraph42 Management GmbH | Unclassified | IPv4 IPv6 | 14,712 |
| AS34250 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 12,170 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 11,665 |
| AS55330 | AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK | Unclassified | IPv4 IPv6 | 10,576 |
| AS34718 | "IST TELEKOM" JV LLC | Unclassified | IPv4 IPv6 | 8,169 |
| AS8449 | "ElCat" Ltd. | Unclassified | IPv4 IPv6 | 5,271 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,759 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 4,642 |
| AS49273 | COSCOM Liability Limited Company | Unclassified | IPv4 IPv6 | 4,358 |
| AS12365 | JC LLC Sarkor-Telecom | Hosting | IPv4 IPv6 | 4,303 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.