asn.dev

Observed topology

AS200970 RIEPERT Riepert Informationstechnologie GmbH

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200970: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv678
AS21013eww agUnclassifiedIPv4 IPv651
AS6939Hurricane Electric LLCTransitIPv414
AS200683Elektro Puehringer GmbHUnclassifiedIPv44
AS24482SG.GSHostingIPv4 IPv63
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv63
AS48362Stadtwerke FeldkirchResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51187HABAU Hoch- und Tiefbau GmbHUnclassifiedIPv459
AS200683Elektro Puehringer GmbHUnclassifiedIPv4 IPv648
AS210982aRanger GmbHUnclassifiedIPv441
AS211984Steinbach international GmbHUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6177
AS21013eww agUnclassifiedIPv4 IPv699
AS51187HABAU Hoch- und Tiefbau GmbHUnclassifiedIPv459
AS200683Elektro Puehringer GmbHUnclassifiedIPv4 IPv655
AS210982aRanger GmbHUnclassifiedIPv441
AS6939Hurricane Electric LLCTransitIPv421
AS211984Steinbach international GmbHUnclassifiedIPv413
AS24482SG.GSHostingIPv4 IPv65
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv61

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.