asn.dev

Observed topology

AS47583 AS-HOSTINGER Hostinger International Limited

Hosting RIPE Content

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

Transit

Upstream networks

All 50

Networks observed carrying traffic for AS47583: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv633,936
AS174Cogent Communications, LLCTransitIPv4 IPv69,242
AS1299Arelion Sweden ABTransitIPv4 IPv66,658
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv66,056
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv65,056
AS12025Iron Mountain Data CenterUnclassifiedIPv4 IPv64,604
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,584
AS24482SG.GSHostingIPv4 IPv64,401
AS5405Inter.link GmbHUnclassifiedIPv4 IPv64,068
AS4800PT Aplikanusa LintasartaHostingIPv4 IPv63,046

Transit

Downstream networks

inferred

Networks for which AS47583 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 50

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv633,936
AS174Cogent Communications, LLCTransitIPv4 IPv69,242
AS1299Arelion Sweden ABTransitIPv4 IPv66,658
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv66,056
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv65,056
AS12025Iron Mountain Data CenterUnclassifiedIPv4 IPv64,604
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,584
AS24482SG.GSHostingIPv4 IPv64,401
AS5405Inter.link GmbHUnclassifiedIPv4 IPv64,068
AS4800PT Aplikanusa LintasartaHostingIPv4 IPv63,046

Provenance

Where this comes from

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