Observed topology
AS267845 Exito Vision Cable S.A.S
Unclassified LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS267845: 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 |
|---|---|---|---|---|
| AS272935 | GB TELECORP DOMINICANA, S.R.L | Unclassified | IPv4 IPv6 | 3,496 |
Transit
Downstream networks
Networks for which AS267845 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS272083 | REYNOSO, S.R.L. | Residential | IPv4 IPv6 | 3,454 |
| AS274105 | LINKZONE, S.R.L. | Unclassified | IPv4 IPv6 | 453 |
| AS274123 | GLOBAL INVERNET SRL | Unclassified | IPv4 IPv6 | 360 |
| AS273224 | BRAVIC SRL | Unclassified | IPv4 IPv6 | 334 |
| AS64120 | NOCPERU-LATIN TECHNOLOGIES | Unclassified | IPv6 | 160 |
| AS272138 | RENOCA GROUP SRL | Unclassified | IPv4 IPv6 | 90 |
| AS275000 | ALB224 | Unclassified | IPv4 IPv6 | 19 |
| AS273158 | INTERSAT DOMINICANA SRL | Unclassified | IPv4 | 5 |
Adjacency
Adjacent networks
Every AS seen directly next to AS267845 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS272935 | GB TELECORP DOMINICANA, S.R.L | Unclassified | IPv4 IPv6 | 8,429 |
| AS272083 | REYNOSO, S.R.L. | Residential | IPv4 IPv6 | 3,512 |
| AS274105 | LINKZONE, S.R.L. | Unclassified | IPv4 IPv6 | 453 |
| AS274123 | GLOBAL INVERNET SRL | Unclassified | IPv4 IPv6 | 360 |
| AS273224 | BRAVIC SRL | Unclassified | IPv4 IPv6 | 334 |
| AS64120 | NOCPERU-LATIN TECHNOLOGIES | Unclassified | IPv6 | 160 |
| AS272138 | RENOCA GROUP SRL | Unclassified | IPv4 IPv6 | 90 |
| AS275000 | ALB224 | Unclassified | IPv4 IPv6 | 19 |
| AS273158 | INTERSAT DOMINICANA SRL | Unclassified | IPv4 | 5 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.