Observed topology
AS12963 VOLZ Scientific -Industrial Firm Volz Ltd
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12963: 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 IPv6 | 1,230 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 340 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 206 |
| AS12741 | Netia SA | Residential | IPv4 IPv6 | 204 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 177 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 82 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 70 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 68 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 40 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 39 |
Transit
Downstream networks
Networks for which AS12963 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8856 | UkrNet Ltd. | Hosting | IPv4 | 650 |
| AS203284 | Gutsal Alexandr Viktorovich | Hosting | IPv4 | 324 |
| AS39066 | OJSC Kredobank | Unclassified | IPv4 | 186 |
| AS34190 | Microcom Ltd. | Unclassified | IPv4 | 135 |
| AS44526 | DOM TELECOM LLC | Unclassified | IPv4 | 134 |
| AS3254 | Lucky Net Ltd | Unclassified | IPv4 | 132 |
| AS29382 | LIMITED LIABILITY COMPANY "UKRAINIAN INFOSYSTEMS" | Unclassified | IPv4 | 132 |
| AS35524 | Trans Traffic Ltd. | Unclassified | IPv4 | 132 |
| AS207577 | LARANS GROUP LLC | Unclassified | IPv4 | 130 |
| AS209912 | IC ARX INSURANCE PJSC | Unclassified | IPv4 | 126 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12963 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35297 | Dataline LLC | Unclassified | IPv4 IPv6 | 4,467 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,078 |
| AS8856 | UkrNet Ltd. | Hosting | IPv4 | 650 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 578 |
| AS12741 | Netia SA | Residential | IPv4 IPv6 | 565 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 405 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 394 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 375 |
| AS29382 | LIMITED LIABILITY COMPANY "UKRAINIAN INFOSYSTEMS" | Unclassified | IPv4 | 354 |
| AS203284 | Gutsal Alexandr Viktorovich | Hosting | IPv4 | 324 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12: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.