asn.dev

Observed topology

AS31463 FOURD-AS

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31463: 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
AS13009Redcentric Solutions LtdUnclassifiedIPv4 IPv62,006
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv697

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25546Brookland Computer Services LimitedUnclassifiedIPv4114
AS42044CentralNic LtdUnclassifiedIPv4 IPv693
AS35241Vostel LimitedUnclassifiedIPv457

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13009Redcentric Solutions LtdUnclassifiedIPv4 IPv62,270
AS25546Brookland Computer Services LimitedUnclassifiedIPv4114
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv697
AS42044CentralNic LtdUnclassifiedIPv4 IPv693
AS35241Vostel LimitedUnclassifiedIPv457

Provenance

Where this comes from

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