asn.dev

Observed topology

AS42229 Cesar Maffini Martin

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42229: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57910Soluciones Corporativas IP, SLResidentialIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4169
AS8637SpainWISP, S.L.UnclassifiedIPv4167
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv45
AS24482SG.GSHostingIPv43
AS50629LWLcom GmbHUnclassifiedIPv41
AS57910Soluciones Corporativas IP, SLResidentialIPv41

Provenance

Where this comes from

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