asn.dev

Observed topology

AS271458 KAIBA ISP TELECOMUNICACOES EIRELI

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271458: 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
AS266409SECW TELECOMUnclassifiedIPv4116
AS10733DC MATRIX INTERNET S/AHostingIPv631
AS24482SG.GSHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270590I.P CONECTA TELECOM LTDAUnclassifiedIPv4 IPv692
AS272529FUTURE FIBRA OPTICA LTDAResidentialIPv67

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266409SECW TELECOMUnclassifiedIPv4223
AS270590I.P CONECTA TELECOM LTDAUnclassifiedIPv4 IPv692
AS272529FUTURE FIBRA OPTICA LTDAResidentialIPv4 IPv688
AS10733DC MATRIX INTERNET S/AHostingIPv671
AS6939Hurricane Electric LLCTransitIPv431
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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