asn.dev

Observed topology

AS208164 formicidae-holdings Formicidae Holdings B.V.

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208164: 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
AS57866Fusix Networks B.V.UnclassifiedIPv4 IPv6117
AS20562Broadband Hosting B.V.HostingIPv4 IPv620
AS12859BIT BVHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS204092Association GRIFONUnclassifiedIPv4 IPv63
AS6696VERIXI SAUnclassifiedIPv42
AS37100SEACOM LimitedUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199700GOOSE B.V.UnclassifiedIPv4 IPv693
AS203071Guardey B.V.UnclassifiedIPv4 IPv693
AS214011Formicidae Holdings B.V.UnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS57866Fusix Networks B.V.UnclassifiedIPv4 IPv6330
AS199700GOOSE B.V.UnclassifiedIPv4 IPv693
AS203071Guardey B.V.UnclassifiedIPv4 IPv693
AS214011Formicidae Holdings B.V.UnclassifiedIPv4 IPv693
AS20562Broadband Hosting B.V.HostingIPv4 IPv656
AS12859BIT BVHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS204092Association GRIFONUnclassifiedIPv4 IPv69
AS6696VERIXI SAUnclassifiedIPv45
AS37100SEACOM LimitedUnclassifiedIPv45

All 11 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.