asn.dev

Observed topology

AS29074 FAUST-ASN FAUST ISP LTD.

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29074: 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
AS41033D2CLOUD NETWORK SERVICES (PTY) LTDHostingIPv4144
AS13249PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv4132
AS6939Hurricane Electric LLCTransitIPv448
AS43668"AS43668" LLCResidentialIPv631
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv67
AS8218Zayo Infrastructure France SAUnclassifiedIPv46
AS34927iFog GmbHHostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25143Company "Zagalni Merezhi" LtdUnclassifiedIPv459
AS12788"NBI INTERNET" LLCUnclassifiedIPv44
AS25199unnamedUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS41033D2CLOUD NETWORK SERVICES (PTY) LTDHostingIPv4169
AS13249PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv4157
AS25143Company "Zagalni Merezhi" LtdUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv456
AS43668"AS43668" LLCResidentialIPv631
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv624
AS24482SG.GSHostingIPv4 IPv68
AS8218Zayo Infrastructure France SAUnclassifiedIPv47
AS34927iFog GmbHHostingIPv47
AS12788"NBI INTERNET" LLCUnclassifiedIPv44

All 11 adjacent →

Provenance

Where this comes from

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