asn.dev

Observed topology

AS207992 FEELB

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207992: 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
AS62000SERVERD SASHostingIPv4 IPv6743
AS35625Eurofiber France SASHostingIPv4 IPv6228
AS6939Hurricane Electric LLCTransitIPv4 IPv6150
AS49434FBW NETWORKS SASUnclassifiedIPv4 IPv696
AS204092Association GRIFONUnclassifiedIPv4 IPv618

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61026HASGARD s.a.r.l.UnclassifiedIPv4200

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv61,315
AS61026HASGARD s.a.r.l.UnclassifiedIPv4 IPv6802
AS49434FBW NETWORKS SASUnclassifiedIPv4 IPv6271
AS35625Eurofiber France SASHostingIPv4 IPv6228
AS6939Hurricane Electric LLCTransitIPv4 IPv6186
AS204092Association GRIFONUnclassifiedIPv4 IPv619
AS6696VERIXI SAUnclassifiedIPv418

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.