asn.dev

Observed topology

AS34372 VEGASYSTEMS-AS

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34372: 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
AS9145EWE TEL GmbHResidentialIPv4 IPv6206
AS88811&1 Versatel GmbHResidentialIPv4 IPv6107
AS3320Deutsche Telekom AGMobileIPv4 IPv683
AS3209Vodafone GmbHResidentialIPv422

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203724Musarubra Germany GmbHUnclassifiedIPv4 IPv6209
AS50800SCI Systems GmbHUnclassifiedIPv459
AS199460Vasgard GmbHUnclassifiedIPv459
AS9182COMSPACE GmbH & Co KGUnclassifiedIPv4 IPv619

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9145EWE TEL GmbHResidentialIPv4 IPv6428
AS203724Musarubra Germany GmbHUnclassifiedIPv4 IPv6209
AS3320Deutsche Telekom AGMobileIPv4 IPv6174
AS88811&1 Versatel GmbHResidentialIPv4 IPv6126
AS50800SCI Systems GmbHUnclassifiedIPv459
AS199460Vasgard GmbHUnclassifiedIPv459
AS3209Vodafone GmbHResidentialIPv447
AS9182COMSPACE GmbH & Co KGUnclassifiedIPv4 IPv630

Provenance

Where this comes from

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