asn.dev

Observed topology

AS31055 CONSULTIX-AS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31055: 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
AS61955ColocationIX GmbHUnclassifiedIPv41,287
AS9145EWE TEL GmbHResidentialIPv4363
AS174Cogent Communications, LLCTransitIPv4332

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204368Joerg Suenram trading as it NGO GmbH & Co. KGUnclassifiedIPv4 IPv643
AS57137SIEVERS-SNC Beteiligungs GmbHUnclassifiedIPv4 IPv634
AS44599Fabio Martin trading as FM-Datacenter GmbH & Co. KGUnclassifiedIPv430
AS50905LAND-DATA Beteiligungs GmbHUnclassifiedIPv430
AS3337ColocationIX GmbHHostingIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61955ColocationIX GmbHUnclassifiedIPv41,287
AS174Cogent Communications, LLCTransitIPv4 IPv6477
AS9145EWE TEL GmbHResidentialIPv4 IPv6365
AS204368Joerg Suenram trading as it NGO GmbH & Co. KGUnclassifiedIPv4 IPv643
AS57137SIEVERS-SNC Beteiligungs GmbHUnclassifiedIPv4 IPv634
AS44599Fabio Martin trading as FM-Datacenter GmbH & Co. KGUnclassifiedIPv430
AS50905LAND-DATA Beteiligungs GmbHUnclassifiedIPv430
AS3337ColocationIX GmbHHostingIPv410

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.