asn.dev

Observed topology

AS62416 PTSERVIDOR

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62416: 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
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv692
AS6939Hurricane Electric LLCTransitIPv4 IPv644
AS5533Claranet Portugal S.AHostingIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv63
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS19577CASTRO TELECOM LLCUnclassifiedIPv459
AS199993Associacao DNS.PTUnclassifiedIPv4 IPv69
AS197000Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv6184
AS19577CASTRO TELECOM LLCUnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS5533Claranet Portugal S.AHostingIPv4 IPv639
AS199993Associacao DNS.PTUnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv65
AS197000Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS25091IP-Max SAUnclassifiedIPv61

Provenance

Where this comes from

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