asn.dev

Observed topology

AS207176 OPENFIBER

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS207176: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv698
AS20562Broadband Hosting B.V.HostingIPv4 IPv670
AS174Cogent Communications, LLCTransitIPv4 IPv657
AS6939Hurricane Electric LLCTransitIPv448
AS35133Eranium B.V.HostingIPv4 IPv647
AS6830Liberty Global Europe Holding B.V.ResidentialIPv416
AS50304Blix Solutions ASUnclassifiedIPv416
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS48185team.blue NVUnclassifiedIPv4 IPv69

All 30 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213577Monta Services BVUnclassifiedIPv430

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv698
AS20562Broadband Hosting B.V.HostingIPv4 IPv676
AS174Cogent Communications, LLCTransitIPv4 IPv665
AS6939Hurricane Electric LLCTransitIPv448
AS35133Eranium B.V.HostingIPv4 IPv647
AS213577Monta Services BVUnclassifiedIPv430
AS6830Liberty Global Europe Holding B.V.ResidentialIPv424
AS50304Blix Solutions ASUnclassifiedIPv416
AS48185team.blue NVUnclassifiedIPv4 IPv613
AS57866Fusix Networks B.V.UnclassifiedIPv412

All 31 adjacent →

Provenance

Where this comes from

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