asn.dev

Observed topology

AS201213 DA-RZ_AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS201213: 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
AS199524G-Core Labs S.A.HostingIPv4 IPv6190
AS8220COLT Technology Services Group LimitedHostingIPv473
AS3356Level 3 Parent, LLCTransitIPv4 IPv662
AS6939Hurricane Electric LLCTransitIPv436
AS3257GTT Communications Inc.TransitIPv432
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv620
AS3320Deutsche Telekom AGMobileIPv4 IPv617
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208676OWH SE i.L.UnclassifiedIPv456

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS199524G-Core Labs S.A.HostingIPv4 IPv6246
AS8220COLT Technology Services Group LimitedHostingIPv473
AS3356Level 3 Parent, LLCTransitIPv4 IPv662
AS208676OWH SE i.L.UnclassifiedIPv456
AS6939Hurricane Electric LLCTransitIPv436
AS3257GTT Communications Inc.TransitIPv432
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv620
AS3320Deutsche Telekom AGMobileIPv4 IPv617
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68

All 21 adjacent →

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.