asn.dev

Observed topology

AS47172 GREENHOST

Residential RIPE Content

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS47172: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6726
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6709
AS6939Hurricane Electric LLCTransitIPv4 IPv6338
AS50304Blix Solutions ASUnclassifiedIPv4 IPv658
AS24482SG.GSHostingIPv4 IPv629
AS20764CJSC RASCOMUnclassifiedIPv428
AS34927iFog GmbHHostingIPv428
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61
AS48185team.blue NVUnclassifiedIPv61
AS48362Stadtwerke FeldkirchResidentialIPv61

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152460Greenhost BVUnclassifiedIPv4727
AS209829Greenhost BVUnclassifiedIPv4666

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv61,276
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv61,068
AS152460Greenhost BVUnclassifiedIPv4727
AS209829Greenhost BVUnclassifiedIPv4666
AS6939Hurricane Electric LLCTransitIPv4 IPv6525
AS50304Blix Solutions ASUnclassifiedIPv4 IPv698
AS24482SG.GSHostingIPv4 IPv651
AS34927iFog GmbHHostingIPv448
AS20764CJSC RASCOMUnclassifiedIPv428
AS37721Virtual Technologies & SolutionsResidentialIPv422

All 23 adjacent →

Provenance

Where this comes from

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