asn.dev

Observed topology

AS44393 Securebit AG

Unclassified RIPE

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

Transit

Upstream networks

inferred

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

inferred

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

ASNetworkTypeFamiliesPaths seen
AS64073Vetta GroupUnclassifiedIPv4 IPv668
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv629
AS401753BIXCE IncUnclassifiedIPv4 IPv627
AS58057Securebit AGUnclassifiedIPv4 IPv614
AS212508Lowhosting services of Davide GennariUnclassifiedIPv45
AS212024Marc SchmittUnclassifiedIPv4 IPv63
AS35710weber.digital GmbHHostingIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58057Securebit AGUnclassifiedIPv4 IPv6766,960
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv6178,523
AS401753BIXCE IncUnclassifiedIPv4 IPv6164,433
AS212024Marc SchmittUnclassifiedIPv4 IPv6114,662
AS35710weber.digital GmbHHostingIPv487,335
AS64073Vetta GroupUnclassifiedIPv4 IPv648,425
AS205794JINZE YANGUnclassifiedIPv68,991
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41,220

Provenance

Where this comes from

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