asn.dev

Observed topology

AS209114 IP-FAST Luiz Fernando Ribeiro Amaral

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209114: 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
AS8893Artfiles New Media GmbHHostingIPv4 IPv684
AS200462Lennart Seitz trading as "ETH-Services"HostingIPv4 IPv660
AS6939Hurricane Electric LLCTransitIPv4 IPv654
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv64
AS6797GlobalConnect ABUnclassifiedIPv43
AS20562Broadband Hosting B.V.HostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202545Yannik SchwiegerUnclassifiedIPv636
AS206072Kajetan StaszkiewiczUnclassifiedIPv636
AS218571Michael HossUnclassifiedIPv611

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6124
AS8893Artfiles New Media GmbHHostingIPv4 IPv686
AS200462Lennart Seitz trading as "ETH-Services"HostingIPv4 IPv667
AS202545Yannik SchwiegerUnclassifiedIPv636
AS206072Kajetan StaszkiewiczUnclassifiedIPv636
AS218571Michael HossUnclassifiedIPv611
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv66
AS6797GlobalConnect ABUnclassifiedIPv43
AS20562Broadband Hosting B.V.HostingIPv43

Provenance

Where this comes from

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