asn.dev

Observed topology

AS3331 OPENXS-AS OpenXS GmbH

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3331: 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
AS1299Arelion Sweden ABTransitIPv4 IPv632
AS3356Level 3 Parent, LLCTransitIPv4 IPv625
AS6939Hurricane Electric LLCTransitIPv4 IPv620
AS88811&1 Versatel GmbHResidentialIPv47
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8956Stadt FlensburgUnclassifiedIPv4 IPv659
AS61377ORION Versand GmbH & Co. KGUnclassifiedIPv458
AS21173LANtana GmbHUnclassifiedIPv448
AS41213edding AGUnclassifiedIPv419

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6102
AS3356Level 3 Parent, LLCTransitIPv4 IPv683
AS8956Stadt FlensburgUnclassifiedIPv4 IPv659
AS61377ORION Versand GmbH & Co. KGUnclassifiedIPv458
AS21173LANtana GmbHUnclassifiedIPv448
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS31027GlobalConnect A/SUnclassifiedIPv424
AS41213edding AGUnclassifiedIPv419
AS88811&1 Versatel GmbHResidentialIPv47
AS24482SG.GSHostingIPv4 IPv65

All 12 adjacent →

Provenance

Where this comes from

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