asn.dev

Observed topology

AS197477 NERDSCAVE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197477: 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
AS6939Hurricane Electric LLCTransitIPv6256
AS197071active 1 GmbHUnclassifiedIPv4 IPv6138
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv697
AS207252Felix GassanUnclassifiedIPv4 IPv693
AS58015Collin Schneeweiss trading as Tievolu GbRUnclassifiedIPv4 IPv658
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv611
AS401753BIXCE IncUnclassifiedIPv4 IPv611
AS56662Marcin GondekUnclassifiedIPv68
AS206499LOCIX LIMITEDUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215563Lukas Buttler trading as Luke IT consultingHostingIPv4 IPv624

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6256
AS197071active 1 GmbHUnclassifiedIPv4 IPv6141
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv697
AS207252Felix GassanUnclassifiedIPv4 IPv693
AS58015Collin Schneeweiss trading as Tievolu GbRUnclassifiedIPv4 IPv679
AS215563Lukas Buttler trading as Luke IT consultingHostingIPv4 IPv624
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv611
AS401753BIXCE IncUnclassifiedIPv4 IPv611
AS56662Marcin GondekUnclassifiedIPv68

All 11 adjacent →

Provenance

Where this comes from

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