asn.dev

Observed topology

AS5463 PERCEVAL

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5463: 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
AS3356Level 3 Parent, LLCTransitIPv454
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS3257GTT Communications Inc.TransitIPv432
AS33891Core-Backbone GmbHHostingIPv44
AS24482SG.GSHostingIPv4 IPv63
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS45049Mohamed El BoudduntiResidentialIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv63

Transit

Downstream networks

inferred

Networks for which AS5463 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv454
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS3257GTT Communications Inc.TransitIPv432
AS33891Core-Backbone GmbHHostingIPv44
AS24482SG.GSHostingIPv4 IPv63
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS45049Mohamed El BoudduntiResidentialIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv63

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-12 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.