asn.dev

Observed topology

AS57793 THIRTEENTEN

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57793: 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
AS25098Netcalibre LtdUnclassifiedIPv4 IPv6567
AS6939Hurricane Electric LLCTransitIPv4 IPv6235
AS61049Exascale LtdResidentialIPv4112
AS33891Core-Backbone GmbHHostingIPv426
AS24482SG.GSHostingIPv4 IPv620
AS48185team.blue NVUnclassifiedIPv4 IPv620
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv620
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv616
AS5511Orange S.A.TransitIPv415
AS20562Broadband Hosting B.V.HostingIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199165Shibboleet LtdUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS25098Netcalibre LtdUnclassifiedIPv4 IPv6567
AS6939Hurricane Electric LLCTransitIPv4 IPv6235
AS61049Exascale LtdResidentialIPv4112
AS33891Core-Backbone GmbHHostingIPv427
AS24482SG.GSHostingIPv4 IPv620
AS48185team.blue NVUnclassifiedIPv4 IPv620
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv620
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv616
AS5511Orange S.A.TransitIPv415
AS20562Broadband Hosting B.V.HostingIPv411

All 11 adjacent →

Provenance

Where this comes from

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