asn.dev

Observed topology

AS26383 ASNET

Unclassified DROP-listed space ARIN

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS26383: 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
AS56630Melbikomas UABHostingIPv4 IPv64,459
AS60068Datacamp LimitedHostingIPv4 IPv63,250
AS57043HOSTKEY B.V.HostingIPv4 IPv63,175
AS8849Melbikomas UABHostingIPv4 IPv61,675
AS36352HostPapaHostingIPv4 IPv61,276
AS44901Belcloud LTDHostingIPv4 IPv61,088
AS63023GTHostHostingIPv4 IPv61,026
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv4 IPv6866
AS209625Redcluster LTDUnclassifiedIPv4515
AS395839HOSTKEYUnclassifiedIPv4 IPv6488

All 18 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS56630Melbikomas UABHostingIPv4 IPv64,459
AS60068Datacamp LimitedHostingIPv4 IPv63,250
AS57043HOSTKEY B.V.HostingIPv4 IPv63,175
AS8849Melbikomas UABHostingIPv4 IPv61,675
AS36352HostPapaHostingIPv4 IPv61,276
AS44901Belcloud LTDHostingIPv4 IPv61,088
AS63023GTHostHostingIPv4 IPv61,026
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv4 IPv6866
AS209625Redcluster LTDUnclassifiedIPv4515
AS395839HOSTKEYUnclassifiedIPv4 IPv6488

All 18 adjacent →

Provenance

Where this comes from

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