asn.dev

Observed topology

AS56755 Securebit AG

Unclassified RIPE Route Server

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS42WoodyNet, Inc.UnclassifiedIPv4 IPv681
AS58057Securebit AGUnclassifiedIPv4 IPv615
AS57050DreamServer S.R.L.UnclassifiedIPv4 IPv611
AS57521Simplysoft GmbHUnclassifiedIPv4 IPv67
AS112DNS-OARCUnclassifiedIPv4 IPv64
AS57222Olaf HaaseUnclassifiedIPv4 IPv64
AS59570Jens ZimperfeldHostingIPv4 IPv64
AS202929Olaf LienauUnclassifiedIPv63
AS215887Serhiy BobrovUnclassifiedIPv63
AS215932David HyruleUnclassifiedIPv63

All 24 downstreams →

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS42WoodyNet, Inc.UnclassifiedIPv4 IPv685
AS209898ungleich glarus agUnclassifiedIPv634
AS58057Securebit AGUnclassifiedIPv4 IPv630
AS57050DreamServer S.R.L.UnclassifiedIPv4 IPv611
AS57521Simplysoft GmbHUnclassifiedIPv4 IPv67
AS612184b42 UGUnclassifiedIPv4 IPv67
AS112DNS-OARCUnclassifiedIPv4 IPv64
AS57222Olaf HaaseUnclassifiedIPv4 IPv64
AS59570Jens ZimperfeldHostingIPv4 IPv64
AS202929Olaf LienauUnclassifiedIPv63

All 24 adjacent →

Provenance

Where this comes from

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