asn.dev

Observed topology

AS24748 Atman Sp. z o.o.

Hosting APNIC

Upstreams 0 carry this network
Downstreams 43 this network carries
Adjacent (IPv4) 26
Adjacent (IPv6) 36
Upstream graph Who carries AS24748, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS24748 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24748: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 43

Networks for which AS24748 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS39507Biznes Swiatlowodem Sp. z o.o.UnclassifiedIPv670
AS15967Nazwa.pl Sp.z.o.o.HostingIPv639
AS13000Leon Sp. z o.o.ResidentialIPv4 IPv621
AS205581CVD Sp. z o.o. Sp.k.UnclassifiedIPv4 IPv618
AS57789HomeNet Technologies Sp. z o.o.ResidentialIPv613
AS199524G-Core Labs S.A.HostingIPv612
AS15694Atman Sp. z o.o.ResidentialIPv68
AS24723Atman Sp. z o.o.HostingIPv66
AS201966OptiKabel Telecom Sp. z o.o.ResidentialIPv46
AS396986Bytedance Inc.HostingIPv66

Adjacency

Adjacent networks

All 53

Every AS seen directly next to AS24748 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6154
AS29632Netassist International EOODUnclassifiedIPv6129
AS15967Nazwa.pl Sp.z.o.o.HostingIPv673
AS39507Biznes Swiatlowodem Sp. z o.o.UnclassifiedIPv670
AS24482SG.GSHostingIPv4 IPv669
AS15694Atman Sp. z o.o.ResidentialIPv4 IPv630
AS20485Joint Stock Company TransTeleComUnclassifiedIPv424
AS13000Leon Sp. z o.o.ResidentialIPv4 IPv621
AS20473The Constant Company, LLCHostingIPv620
AS205581CVD Sp. z o.o. Sp.k.UnclassifiedIPv4 IPv618

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.