asn.dev

Observed topology

AS265975 AS265975 - INTEREDE TELECOM

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265975: 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
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv4 IPv6438
AS3356Level 3 Parent, LLCTransitIPv4 IPv647
AS6939Hurricane Electric LLCTransitIPv628
AS24482SG.GSHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264331INTEREDE TELECOMUnclassifiedIPv4 IPv6453
AS273704RRNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv672
AS265014GNA TELECOM LTDA - MEUnclassifiedIPv42
AS267618I9-NETCEL TELECOMUNICACOES LTDAUnclassifiedIPv62

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264409Huge Solucoes Corporativas LtdaUnclassifiedIPv4 IPv6977
AS264331INTEREDE TELECOMUnclassifiedIPv4 IPv6453
AS3356Level 3 Parent, LLCTransitIPv4 IPv678
AS273704RRNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv672
AS6939Hurricane Electric LLCTransitIPv4 IPv635
AS267618I9-NETCEL TELECOMUNICACOES LTDAUnclassifiedIPv65
AS37721Virtual Technologies & SolutionsResidentialIPv64
AS24482SG.GSHostingIPv4 IPv63
AS265014GNA TELECOM LTDA - MEUnclassifiedIPv42

Provenance

Where this comes from

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