asn.dev

Observed topology

AS207487 ROUTING-CAFE

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS207487: 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
AS200132Peter-Paul Maria KurstjensUnclassifiedIPv4 IPv675
AS8283Netwerkvereniging ColoclueUnclassifiedIPv4 IPv650
AS6939Hurricane Electric LLCTransitIPv46
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64
AS58057Securebit AGUnclassifiedIPv4 IPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18607Gustav CaplanUnclassifiedIPv637

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS200132Peter-Paul Maria KurstjensUnclassifiedIPv4 IPv697
AS8283Netwerkvereniging ColoclueUnclassifiedIPv4 IPv661
AS18607Gustav CaplanUnclassifiedIPv637
AS6939Hurricane Electric LLCTransitIPv46
AS24482SG.GSHostingIPv4 IPv65
AS58057Securebit AGUnclassifiedIPv4 IPv65
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

Provenance

Where this comes from

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