asn.dev

Observed topology

AS207375 FIBO

Residential RIPE

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS207375: 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
AS2914NTT America, Inc.TransitIPv4 IPv61,158
AS6939Hurricane Electric LLCTransitIPv4 IPv6489
AS174Cogent Communications, LLCTransitIPv4 IPv6447
AS6461Zayo BandwidthTransitIPv4153
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6108
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv654
AS24482SG.GSHostingIPv4 IPv654
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv654
AS48185team.blue NVUnclassifiedIPv4 IPv654
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv654

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206238Freedom Internet BVResidentialIPv4 IPv6141

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv61,204
AS174Cogent Communications, LLCTransitIPv4 IPv6493
AS6939Hurricane Electric LLCTransitIPv4 IPv6489
AS6461Zayo BandwidthTransitIPv4153
AS206238Freedom Internet BVResidentialIPv4 IPv6141
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6132
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv678
AS24482SG.GSHostingIPv4 IPv654
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv654
AS48185team.blue NVUnclassifiedIPv4 IPv654

Provenance

Where this comes from

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