asn.dev

Observed topology

AS31554 LANSOFT LANSOFT NETWORK

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31554: 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
AS6204INTERKVM HOST SRLUnclassifiedIPv4 IPv6872
AS6939Hurricane Electric LLCTransitIPv4 IPv6148
AS3356Level 3 Parent, LLCTransitIPv472
AS24482SG.GSHostingIPv4 IPv620
AS20764CJSC RASCOMUnclassifiedIPv418

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40975CHML Web Services SRLHostingIPv4 IPv6360
AS214368Oleksandr RadchenkoUnclassifiedIPv4 IPv6268
AS39629LANSOFT DATA SRLUnclassifiedIPv4 IPv6129

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6204INTERKVM HOST SRLUnclassifiedIPv4 IPv61,096
AS40975CHML Web Services SRLHostingIPv4 IPv6360
AS6939Hurricane Electric LLCTransitIPv4 IPv6308
AS214368Oleksandr RadchenkoUnclassifiedIPv4 IPv6268
AS1299Arelion Sweden ABTransitIPv4234
AS3356Level 3 Parent, LLCTransitIPv4 IPv6172
AS39629LANSOFT DATA SRLUnclassifiedIPv4 IPv6129
AS24482SG.GSHostingIPv4 IPv636
AS20764CJSC RASCOMUnclassifiedIPv430
AS8708DIGI ROMANIA S.A.MobileIPv411

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.