Observed topology
AS49963 BELRTS BELRTS Ltd
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49963: 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 |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 150 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 100 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 44 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 6 |
| AS24482 | SG.GS | Hosting | IPv4 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 5 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 5 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS49963 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208541 | LLC IT-Media | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49963 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 150 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 101 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 44 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 6 |
| AS24482 | SG.GS | Hosting | IPv4 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 5 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 5 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 5 |
| AS208541 | LLC IT-Media | Unclassified | IPv4 | 1 |
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.