asn.dev

Observed topology

AS47697 BIX-BG-E

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47697: 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
AS8262Evolink EADUnclassifiedIPv4 IPv6162
AS31287IPACCT CABLE LtdUnclassifiedIPv4 IPv6137
AS9070Cooolbox ADResidentialIPv438
AS6939Hurricane Electric LLCTransitIPv437
AS3303Swisscom (Schweiz) AGResidentialIPv45
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2121Reseaux IP Europeens Network Coordination Centre (RIPE NCC)HostingIPv4 IPv695
AS15669BIX.BG Ltd.UnclassifiedIPv4 IPv668
AS1288Packet Clearing House, Inc.UnclassifiedIPv449

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8262Evolink EADUnclassifiedIPv4 IPv6274
AS31287IPACCT CABLE LtdUnclassifiedIPv4 IPv6200
AS2121Reseaux IP Europeens Network Coordination Centre (RIPE NCC)HostingIPv4 IPv695
AS15669BIX.BG Ltd.UnclassifiedIPv4 IPv668
AS6939Hurricane Electric LLCTransitIPv4 IPv661
AS1288Packet Clearing House, Inc.UnclassifiedIPv449
AS9070Cooolbox ADResidentialIPv447
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv64
AS8218Zayo Infrastructure France SAUnclassifiedIPv61

Provenance

Where this comes from

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