asn.dev

Observed topology

AS269843 AS269843 - BANTEL SAC

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269843: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6498
AS273976FICOM TELECOMUNICACIONES S.A.C.UnclassifiedIPv4 IPv6325
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6235
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv679
AS23520Columbus Networks USA, Inc.ResidentialIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272085TELECOMUNICACIONES DEL FUTURO SACUnclassifiedIPv4228
AS274933WASY TECHNOLOGY S.A.C.UnclassifiedIPv4 IPv697

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6505
AS3356Level 3 Parent, LLCTransitIPv4 IPv6498
AS273976FICOM TELECOMUNICACIONES S.A.C.UnclassifiedIPv4 IPv6422
AS272085TELECOMUNICACIONES DEL FUTURO SACUnclassifiedIPv4228
AS273133CONEX TV E.I.R.L.ResidentialIPv4114
AS274933WASY TECHNOLOGY S.A.C.UnclassifiedIPv4 IPv697
AS23520Columbus Networks USA, Inc.ResidentialIPv486
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv679

Provenance

Where this comes from

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