asn.dev

Observed topology

AS39647 REDHOSTING-AS

Hosting RIPE

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS39647: 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
AS24785Broadband Hosting B.V.HostingIPv4 IPv6902
AS20562Broadband Hosting B.V.HostingIPv4 IPv6578
AS6939Hurricane Electric LLCTransitIPv4 IPv6444
AS174Cogent Communications, LLCTransitIPv4 IPv6392
AS200020Stichting NBIP-NaWasUnclassifiedIPv4177
AS8455atom86 BVHostingIPv4 IPv6129
AS44530HOPUS SASUnclassifiedIPv4 IPv6119
AS48185team.blue NVUnclassifiedIPv4 IPv663
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv663
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv663

All 30 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51050H4Hosting BVUnclassifiedIPv4 IPv6136
AS197016Provincie FrieslandUnclassifiedIPv4 IPv688

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS24785Broadband Hosting B.V.HostingIPv4 IPv6918
AS20562Broadband Hosting B.V.HostingIPv4 IPv6653
AS6939Hurricane Electric LLCTransitIPv4 IPv6464
AS174Cogent Communications, LLCTransitIPv4 IPv6408
AS200020Stichting NBIP-NaWasUnclassifiedIPv4177
AS8455atom86 BVHostingIPv4 IPv6140
AS51050H4Hosting BVUnclassifiedIPv4 IPv6136
AS44530HOPUS SASUnclassifiedIPv4 IPv6122
AS197016Provincie FrieslandUnclassifiedIPv4 IPv688
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv674

All 32 adjacent →

Provenance

Where this comes from

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