Observed topology
AS24724 ATMAN-FOREIGN-AS ATM S.A.
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS24724: 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 | 59 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 36 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 19 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 12 |
| AS1836 | green.ch AG | Residential | IPv4 | 3 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 3 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 3 |
| AS6696 | VERIXI SA | Unclassified | IPv4 | 3 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 3 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS24724 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197155 | Artnet Sp. z o.o. | Hosting | IPv4 | 799 |
| AS50599 | DATASPACE P.S.A. | Unclassified | IPv4 IPv6 | 329 |
| AS24723 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 314 |
| AS197431 | GEMIUS SA | Unclassified | IPv4 IPv6 | 240 |
| AS31505 | Przedsiebiorstwo Produkcyjno-Uslugowo-Handlowe 'Duna' Dunaj Piotr | Unclassified | IPv4 | 196 |
| AS48896 | dhosting.pl Sp. z o.o. | Unclassified | IPv4 IPv6 | 184 |
| AS50153 | NET BIS SP Z O O | Residential | IPv4 | 169 |
| AS42830 | STK "TV SAT 364" | Residential | IPv4 IPv6 | 145 |
| AS202081 | GOG sp. z o.o | Hosting | IPv4 | 145 |
| AS48487 | LoVo Sp. z o.o. | Unclassified | IPv4 | 132 |
Adjacency
Adjacent networks
Every AS seen directly next to AS24724 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197155 | Artnet Sp. z o.o. | Hosting | IPv4 | 2,039 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,009 |
| AS15694 | Atman Sp. z o.o. | Residential | IPv4 IPv6 | 992 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 808 |
| AS24723 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 628 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 553 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 553 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 510 |
| AS6696 | VERIXI SA | Unclassified | IPv4 | 491 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 412 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.