Observed topology
AS209116 WEBPRO-AS LLC WEB PRO
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS209116: 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 |
|---|---|---|---|---|
| AS35297 | Dataline LLC | Unclassified | IPv4 | 43 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 9 |
| AS21497 | PrJSC "VF UKRAINE" | Mobile | IPv4 | 4 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 3 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 1 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 1 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS209116 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43332 | LLC "ID STRATEGY" | Unclassified | IPv4 | 240 |
| AS21096 | The State Cyber Protection Center of the State Service of Special Communication and Information Protection of Ukraine | Unclassified | IPv4 | 195 |
| AS62096 | Military unit A0351 | Unclassified | IPv4 | 60 |
| AS58221 | LLC Fiber Group UA | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS209116 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35297 | Dataline LLC | Unclassified | IPv4 | 488 |
| AS43332 | LLC "ID STRATEGY" | Unclassified | IPv4 | 278 |
| AS21096 | The State Cyber Protection Center of the State Service of Special Communication and Information Protection of Ukraine | Unclassified | IPv4 | 234 |
| AS62096 | Military unit A0351 | Unclassified | IPv4 | 60 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 50 |
| AS21497 | PrJSC "VF UKRAINE" | Mobile | IPv4 | 39 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 24 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 15 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 15 |
| AS58221 | LLC Fiber Group UA | Unclassified | IPv4 | 13 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 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.