Observed topology
AS48347 MTW-AS
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS48347: 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 |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 3,619 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 813 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 592 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 280 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 168 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 85 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 83 |
| AS57724 | DDOS-GUARD LTD | Unclassified | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS48347 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42148 | Beirel Telecom LLC | Unclassified | IPv4 IPv6 | 740 |
| AS210028 | LLC "Complex Systems" | Unclassified | IPv4 | 455 |
| AS207676 | Best Line Ltd. | Unclassified | IPv4 | 296 |
| AS41639 | Limited Liability Company Incomsvyaz | Unclassified | IPv4 IPv6 | 281 |
| AS43667 | Vermont-IT Limited Liability Company | Unclassified | IPv4 | 225 |
| AS51579 | Korporatvniy partner Ltd | Unclassified | IPv4 IPv6 | 169 |
| AS62444 | Virtal LLC | Unclassified | IPv4 IPv6 | 167 |
| AS50668 | Dialog-K LLC | Unclassified | IPv4 | 165 |
| AS43865 | Intek-M LLC | Unclassified | IPv4 | 160 |
| AS219477 | Alexey Andreevich Shantora | Unclassified | IPv4 IPv6 | 102 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48347 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 6,254 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 1,403 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 903 |
| AS42148 | Beirel Telecom LLC | Unclassified | IPv4 IPv6 | 802 |
| AS210028 | LLC "Complex Systems" | Unclassified | IPv4 | 455 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 442 |
| AS51579 | Korporatvniy partner Ltd | Unclassified | IPv4 IPv6 | 309 |
| AS207676 | Best Line Ltd. | Unclassified | IPv4 | 296 |
| AS41639 | Limited Liability Company Incomsvyaz | Unclassified | IPv4 IPv6 | 281 |
| AS50668 | Dialog-K LLC | Unclassified | IPv4 | 228 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.