Observed topology
AS42532 VEESP-LV-AS SIA VEESP
Hosting RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS42532: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,132 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 466 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 76 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 56 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 46 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 34 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 31 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 30 |
| AS3399 | Obenet AB | Unclassified | IPv4 | 30 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 30 |
Transit
Downstream networks
Networks for which AS42532 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198130 | Salimov Rustam Khayriddinovich | Unclassified | IPv4 | 792 |
| AS206787 | IP Odintsov Stepan Vladimirovich | Unclassified | IPv4 | 775 |
| AS209183 | AkhaliNet LLC | Unclassified | IPv4 IPv6 | 739 |
| AS210751 | Loginov Kirill Denisovich | Unclassified | IPv4 | 631 |
| AS216253 | Interhive OU | Unclassified | IPv4 | 305 |
| AS219443 | Ints Danebergs | Unclassified | IPv4 IPv6 | 251 |
| AS205290 | NAOBOROT LLP | Unclassified | IPv4 | 184 |
| AS203614 | NEXTTRANSLATE LTD | Unclassified | IPv4 | 183 |
| AS219054 | Nakamoto LLP | Unclassified | IPv4 | 183 |
| AS206715 | UXHOST LTD | Unclassified | IPv4 IPv6 | 156 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42532 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 4,546 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 974 |
| AS198130 | Salimov Rustam Khayriddinovich | Unclassified | IPv4 | 792 |
| AS206787 | IP Odintsov Stepan Vladimirovich | Unclassified | IPv4 | 775 |
| AS209183 | AkhaliNet LLC | Unclassified | IPv4 IPv6 | 739 |
| AS210751 | Loginov Kirill Denisovich | Unclassified | IPv4 | 631 |
| AS216253 | Interhive OU | Unclassified | IPv4 | 305 |
| AS219443 | Ints Danebergs | Unclassified | IPv4 IPv6 | 251 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 236 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 210 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M 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.