Observed topology
AS12695 DINET-AS
Hosting APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS12695: 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 |
|---|---|---|---|---|
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 2,860 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1,296 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 845 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 369 |
| AS31133 | PJSC MegaFon | Mobile | IPv6 | 276 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 131 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 131 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 128 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 128 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 128 |
Transit
Downstream networks
Networks for which AS12695 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211183 | AdminVPS OOO | Unclassified | IPv4 | 531 |
| AS48209 | OOO LANCRONIX | Unclassified | IPv4 | 502 |
| AS43297 | VDS-Telecom LLC. | Unclassified | IPv4 | 453 |
| AS201186 | LLC Digital Network | Unclassified | IPv4 | 300 |
| AS47839 | Zet Maximum limited | Unclassified | IPv4 | 240 |
| AS15850 | Cyberplat OOO | Unclassified | IPv4 | 180 |
| AS49400 | PageMaster Ltd | Unclassified | IPv4 | 180 |
| AS208092 | Global Consult Group LLC | Unclassified | IPv4 | 120 |
| AS50955 | Individual Entrepreneur Iugov Denis Sergeevich | Unclassified | IPv4 IPv6 | 97 |
| AS207209 | IT-Zavod LLC | Unclassified | IPv4 IPv6 | 97 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12695 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 4,453 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 2,100 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,203 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 673 |
| AS211183 | AdminVPS OOO | Unclassified | IPv4 | 531 |
| AS48209 | OOO LANCRONIX | Unclassified | IPv4 | 502 |
| AS43297 | VDS-Telecom LLC. | Unclassified | IPv4 | 453 |
| AS31133 | PJSC MegaFon | Mobile | IPv6 | 374 |
| AS201186 | LLC Digital Network | Unclassified | IPv4 | 300 |
| AS47839 | Zet Maximum limited | Unclassified | IPv4 | 240 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.