asn.dev

Observed topology

AS207866 InCompanyMedia InCompanyMedia B.V.

Hosting RIPE Content

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS207866: 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
AS174Cogent Communications, LLCTransitIPv4 IPv688
AS20562Broadband Hosting B.V.HostingIPv448
AS6939Hurricane Electric LLCTransitIPv418
AS24785Broadband Hosting B.V.HostingIPv418
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv43
AS6696VERIXI SAUnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS24482SG.GSHostingIPv43
AS34927iFog GmbHHostingIPv43
AS37100SEACOM LimitedUnclassifiedIPv43

All 15 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv688
AS20562Broadband Hosting B.V.HostingIPv448
AS6939Hurricane Electric LLCTransitIPv418
AS24785Broadband Hosting B.V.HostingIPv418
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv43
AS6696VERIXI SAUnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS24482SG.GSHostingIPv43
AS34927iFog GmbHHostingIPv43
AS37100SEACOM LimitedUnclassifiedIPv43

All 15 adjacent →

Provenance

Where this comes from

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