asn.dev

Observed topology

AS208258 ACCESS2IT Access2.IT Network

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208258: 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
AS55285Serverside.comUnclassifiedIPv4 IPv6455
AS398465Rackdog, LLCResidentialIPv4 IPv695
AS50917Diederik Focko de ZeeUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210489Beyond Relationship Marketing GmbHUnclassifiedIPv41,392
AS205406Access2.IT Group B.V.UnclassifiedIPv4 IPv6845
AS216459Marketing Mind Online GmbHUnclassifiedIPv4638
AS210970mosento LTDUnclassifiedIPv4290
AS212856Valentin D'EmmanueleUnclassifiedIPv6127
AS213985Rhein-Medial GmbHUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55285Serverside.comUnclassifiedIPv4 IPv63,804
AS210489Beyond Relationship Marketing GmbHUnclassifiedIPv41,392
AS205406Access2.IT Group B.V.UnclassifiedIPv4 IPv6845
AS216459Marketing Mind Online GmbHUnclassifiedIPv4638
AS210970mosento LTDUnclassifiedIPv4290
AS212856Valentin D'EmmanueleUnclassifiedIPv6127
AS398465Rackdog, LLCResidentialIPv4 IPv695
AS213985Rhein-Medial GmbHUnclassifiedIPv458
AS50917Diederik Focko de ZeeUnclassifiedIPv62

Provenance

Where this comes from

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