asn.dev

Observed topology

AS201843 IBERSONTEL

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201843: 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
AS6939Hurricane Electric LLCTransitIPv4676
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4538
AS174Cogent Communications, LLCTransitIPv4466
AS34549meerfarbig GmbH & Co. KGHostingIPv490
AS24482SG.GSHostingIPv430
AS37721Virtual Technologies & SolutionsResidentialIPv430
AS33891Core-Backbone GmbHHostingIPv46
AS5405Inter.link GmbHUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58128COMUNICACIONES PAQUILLO E HIJOS S.L.UnclassifiedIPv4354
AS203051DIPUTACION PROVINCIAL DE AVILAUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4784
AS6939Hurricane Electric LLCTransitIPv4713
AS174Cogent Communications, LLCTransitIPv4602
AS58128COMUNICACIONES PAQUILLO E HIJOS S.L.UnclassifiedIPv4354
AS34549meerfarbig GmbH & Co. KGHostingIPv490
AS203051DIPUTACION PROVINCIAL DE AVILAUnclassifiedIPv465
AS24482SG.GSHostingIPv430
AS37721Virtual Technologies & SolutionsResidentialIPv430
AS33891Core-Backbone GmbHHostingIPv46
AS5405Inter.link GmbHUnclassifiedIPv41

Provenance

Where this comes from

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