asn.dev

Observed topology

AS203993 STEFFANN-DC-AS

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203993: 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
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv679
AS12414Solcon Internetdiensten B.V.ResidentialIPv4 IPv638
AS6939Hurricane Electric LLCTransitIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv68
AS58057Securebit AGUnclassifiedIPv4 IPv68
AS34019Hivane AssociationUnclassifiedIPv4 IPv65
AS202365Omer GOLGELIUnclassifiedIPv44
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS80386connect, Inc.HostingIPv4 IPv681

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6144
AS80386connect, Inc.HostingIPv4 IPv681
AS12414Solcon Internetdiensten B.V.ResidentialIPv4 IPv638
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS24482SG.GSHostingIPv4 IPv610
AS58057Securebit AGUnclassifiedIPv4 IPv610
AS34019Hivane AssociationUnclassifiedIPv4 IPv66
AS202365Omer GOLGELIUnclassifiedIPv45
AS34927iFog GmbHHostingIPv42
AS5405Inter.link GmbHUnclassifiedIPv61

Provenance

Where this comes from

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