Observed topology
AS15694 ATMAN-ISP-AS ATM S.A.
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS15694: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 805 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 550 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 292 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 128 |
| AS24724 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 127 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 47 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 47 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 46 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 46 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 46 |
Transit
Downstream networks
Networks for which AS15694 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57367 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 2,417 |
| AS41079 | Cyber_Folks S.A. | Hosting | IPv4 | 980 |
| AS41745 | Baykov Ilya Sergeevich | Unclassified | IPv4 | 540 |
| AS30851 | Sileman Sp. z o.o. | Unclassified | IPv4 | 523 |
| AS49720 | Gigacloud LLC | Unclassified | IPv4 IPv6 | 402 |
| AS41959 | PLJ TELECOM sp. z o.o. | Residential | IPv4 | 325 |
| AS34342 | Atman Sp. z o.o. | Unclassified | IPv4 | 297 |
| AS31628 | Getfiber Sp. z o.o. | Unclassified | IPv4 | 225 |
| AS197811 | PL.2012+ Sp. z o.o. | Unclassified | IPv4 | 204 |
| AS24929 | IT arte Sp. z o.o. | Hosting | IPv4 | 196 |
Adjacency
Adjacent networks
Every AS seen directly next to AS15694 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 5,678 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,401 |
| AS57367 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 2,428 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,572 |
| AS41079 | Cyber_Folks S.A. | Hosting | IPv4 | 980 |
| AS24724 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 975 |
| AS30851 | Sileman Sp. z o.o. | Unclassified | IPv4 | 857 |
| AS41745 | Baykov Ilya Sergeevich | Unclassified | IPv4 | 540 |
| AS49720 | Gigacloud LLC | Unclassified | IPv4 IPv6 | 464 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 393 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.