asn.dev

Observed topology

AS208348 DOMYNET-AS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208348: 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
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4225
AS174Cogent Communications, LLCTransitIPv480
AS50606Horyzont Technologie Internetowe sp.z.o.o.UnclassifiedIPv415
AS24482SG.GSHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208020Immunity Systems sp. z o.o.UnclassifiedIPv458
AS209399Jaroslaw Legosz trading as Prime ISPUnclassifiedIPv49

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4225
AS174Cogent Communications, LLCTransitIPv4107
AS208020Immunity Systems sp. z o.o.UnclassifiedIPv458
AS50606Horyzont Technologie Internetowe sp.z.o.o.UnclassifiedIPv441
AS6939Hurricane Electric LLCTransitIPv410
AS209399Jaroslaw Legosz trading as Prime ISPUnclassifiedIPv49
AS24482SG.GSHostingIPv46
AS33891Core-Backbone GmbHHostingIPv43

Provenance

Where this comes from

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