Observed topology
AS265695 AS265695 - ELIAS COMUNICACIONES, SRL
Unclassified ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS265695: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS64126 | DOMINICAN TELECOM PRIME, DTP, S.R.L. | Unclassified | IPv4 IPv6 | 378 |
Transit
Downstream networks
Networks for which AS265695 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS273867 | ADOTIC ASOCIACION DOMINICANA DE EMPRESAS DE TECNOLOGIAS DE INFORMACION Y COMUNICACION (STIX) | Hosting | IPv4 IPv6 | 236 |
| AS63293 | Facebook, Inc. | Hosting | IPv4 IPv6 | 88 |
| AS273902 | CONECTIVIDAD DEL CARIBE CONECAR SRL | Unclassified | IPv4 IPv6 | 86 |
| AS274964 | COMPANIA INTERNACIONAL TECNOLOGICA, COITNET, E.I.R.L. | Unclassified | IPv4 IPv6 | 86 |
Adjacency
Adjacent networks
Every AS seen directly next to AS265695 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS64126 | DOMINICAN TELECOM PRIME, DTP, S.R.L. | Unclassified | IPv4 IPv6 | 874 |
| AS273867 | ADOTIC ASOCIACION DOMINICANA DE EMPRESAS DE TECNOLOGIAS DE INFORMACION Y COMUNICACION (STIX) | Hosting | IPv4 IPv6 | 236 |
| AS63293 | Facebook, Inc. | Hosting | IPv4 IPv6 | 88 |
| AS273902 | CONECTIVIDAD DEL CARIBE CONECAR SRL | Unclassified | IPv4 IPv6 | 86 |
| AS274964 | COMPANIA INTERNACIONAL TECNOLOGICA, COITNET, E.I.R.L. | Unclassified | IPv4 IPv6 | 86 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.