asn.dev

Observed topology

AS12817 GEFOEKOM GeFoekoM e.V.

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12817: 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
AS34927iFog GmbHHostingIPv4 IPv661
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS24482SG.GSHostingIPv4 IPv62
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv62
AS202365Omer GOLGELIUnclassifiedIPv41
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29317Sascha LenzUnclassifiedIPv4 IPv6220

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29317Sascha LenzUnclassifiedIPv4 IPv6220
AS34927iFog GmbHHostingIPv4 IPv6219
AS6939Hurricane Electric LLCTransitIPv4 IPv679
AS24482SG.GSHostingIPv4 IPv66
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv66
AS202365Omer GOLGELIUnclassifiedIPv44
AS212508Lowhosting services of Davide GennariUnclassifiedIPv44

Provenance

Where this comes from

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