asn.dev

Observed topology

AS53340 FIBERHUB

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53340: 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
AS53667FranTech SolutionsHostingIPv42,600
AS6939Hurricane Electric LLCTransitIPv4 IPv6302
AS18530Isomedia, Inc.HostingIPv443
AS9002RETN LimitedUnclassifiedIPv42
AS24482SG.GSHostingIPv4 IPv62
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv62
AS293ESnetUnclassifiedIPv41
AS3130RGnet OUUnclassifiedIPv41
AS7575Australian Academic and Research Network (AARNet)EducationIPv41
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397373H4Y Technologies LLCHostingIPv4 IPv6622
AS399804HostodoUnclassifiedIPv4 IPv6399
AS36114VegasNAP, LLCHostingIPv4 IPv6232
AS200019ALEXHOST S.R.L.UnclassifiedIPv4 IPv6231
AS398304The IT GuyUnclassifiedIPv438

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS53667FranTech SolutionsHostingIPv43,928
AS397373H4Y Technologies LLCHostingIPv4 IPv6687
AS6939Hurricane Electric LLCTransitIPv4 IPv6561
AS399804HostodoUnclassifiedIPv4 IPv6399
AS36114VegasNAP, LLCHostingIPv4 IPv6232
AS200019ALEXHOST S.R.L.UnclassifiedIPv4 IPv6231
AS18530Isomedia, Inc.HostingIPv443
AS398304The IT GuyUnclassifiedIPv438
AS9002RETN LimitedUnclassifiedIPv42
AS24482SG.GSHostingIPv4 IPv62

All 15 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.