asn.dev

Observed topology

AS197155 ARTNET Artnet Sp. z o.o.

Hosting RIPE Content

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

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6998
AS24724Atman Sp. z o.o.HostingIPv4920
AS9002RETN LimitedUnclassifiedIPv4 IPv6772
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv695
AS20804Exatel S.A.UnclassifiedIPv4 IPv655
AS6939Hurricane Electric LLCTransitIPv611
AS24482SG.GSHostingIPv61
AS24748Atman Sp. z o.o.HostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200088Artnet Sp. z o.o.UnclassifiedIPv4 IPv61,989

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS200088Artnet Sp. z o.o.UnclassifiedIPv4 IPv64,802
AS174Cogent Communications, LLCTransitIPv4 IPv62,610
AS24724Atman Sp. z o.o.HostingIPv42,334
AS9002RETN LimitedUnclassifiedIPv4 IPv61,964
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv6276
AS6939Hurricane Electric LLCTransitIPv4 IPv6256
AS20804Exatel S.A.UnclassifiedIPv4 IPv6166
AS24482SG.GSHostingIPv4 IPv637
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv64
AS29649Limes sp. z o.o.UnclassifiedIPv43

All 12 adjacent →

Provenance

Where this comes from

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