asn.dev

Observed topology

AS60431 PNO-AS

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS60431: 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 IPv695
AS41495Faelix LimitedUnclassifiedIPv635
AS174Cogent Communications, LLCTransitIPv4 IPv629
AS50917Diederik Focko de ZeeUnclassifiedIPv4 IPv624
AS34927iFog GmbHHostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv64
AS25091IP-Max SAUnclassifiedIPv62
AS209735Lagrange Cloud Technologies LimitedHostingIPv62
AS1103SURF B.V.UnclassifiedIPv41
AS20764CJSC RASCOMUnclassifiedIPv41

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204931PNO Solutions LimitedUnclassifiedIPv669

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv695
AS204931PNO Solutions LimitedUnclassifiedIPv669
AS209735Lagrange Cloud Technologies LimitedHostingIPv638
AS41495Faelix LimitedUnclassifiedIPv635
AS56630Melbikomas UABHostingIPv633
AS174Cogent Communications, LLCTransitIPv4 IPv629
AS50917Diederik Focko de ZeeUnclassifiedIPv4 IPv624
AS34927iFog GmbHHostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv64
AS25091IP-Max SAUnclassifiedIPv62

All 15 adjacent →

Provenance

Where this comes from

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