asn.dev

Observed topology

AS197063 AS-PFALZCONNECT

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS197063: 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
AS12941intersaar GmbHResidentialIPv4 IPv6505
AS6939Hurricane Electric LLCTransitIPv418
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS33891Core-Backbone GmbHHostingIPv44
AS12859BIT BVHostingIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv63
AS212024Marc SchmittUnclassifiedIPv4 IPv63
AS1836green.ch AGResidentialIPv42

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214932Mawacon GmbHUnclassifiedIPv4 IPv696

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS12941intersaar GmbHResidentialIPv4 IPv6570
AS214932Mawacon GmbHUnclassifiedIPv4 IPv696
AS6939Hurricane Electric LLCTransitIPv426
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv68
AS33891Core-Backbone GmbHHostingIPv46
AS12859BIT BVHostingIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS34019Hivane AssociationUnclassifiedIPv4 IPv65
AS212024Marc SchmittUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

All 18 adjacent →

Provenance

Where this comes from

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