asn.dev

Observed topology

AS197922 TECHCREA-SOLUTIONS Techcrea Solutions SAS

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197922: 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
AS25091IP-Max SAUnclassifiedIPv4 IPv61,075
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4486
AS6939Hurricane Electric LLCTransitIPv4 IPv6182
AS24482SG.GSHostingIPv4 IPv630
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv630
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv630
AS204092Association GRIFONUnclassifiedIPv4 IPv630
AS44530HOPUS SASUnclassifiedIPv429
AS12779IT.Gate S.p.A.UnclassifiedIPv42
AS9002RETN LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57265STORYBEL SNCHostingIPv4 IPv697

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS25091IP-Max SAUnclassifiedIPv4 IPv61,150
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4508
AS6939Hurricane Electric LLCTransitIPv4 IPv6182
AS57265STORYBEL SNCHostingIPv4 IPv697
AS24482SG.GSHostingIPv4 IPv630
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv630
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv630
AS204092Association GRIFONUnclassifiedIPv4 IPv630
AS44530HOPUS SASUnclassifiedIPv429
AS12779IT.Gate S.p.A.UnclassifiedIPv42

All 11 adjacent →

Provenance

Where this comes from

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