asn.dev

Observed topology

AS197195 UMBRELLA-NETWORKS VibeGAMES B.V.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197195: 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
AS48925VibeGAMES B.V.HostingIPv460
AS174Cogent Communications, LLCTransitIPv444
AS3356Level 3 Parent, LLCTransitIPv432
AS2914NTT America, Inc.TransitIPv422
AS207994Blockchain Creek B.V.HostingIPv413
AS6939Hurricane Electric LLCTransitIPv48
AS24482SG.GSHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207994Blockchain Creek B.V.HostingIPv467
AS214034KirieLABS CommVUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS207994Blockchain Creek B.V.HostingIPv490
AS174Cogent Communications, LLCTransitIPv489
AS3356Level 3 Parent, LLCTransitIPv482
AS48925VibeGAMES B.V.HostingIPv460
AS214034KirieLABS CommVUnclassifiedIPv460
AS2914NTT America, Inc.TransitIPv454
AS6939Hurricane Electric LLCTransitIPv416
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Provenance

Where this comes from

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