SUBNET.IM

165.182.0.0/16

CODELCO ChuquicamataAS52226

Telmex Chile Internet S.A.AS6429

Announced by more than one origin AS (MOAS).

At a glance

Addresses

65,536

/16 block

Visibility

57%

46 of 80 vantage points

RPKI

No ROA

Registry

LACNICCL

Allocated 26th July 1993

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

  1. London, UK522261425967628529This path
  2. Oregon, US5222614259693920130This path
  3. Amsterdam642927978645334549213151This path
  4. Sao Paulo522261425926258952468266213This path
  5. Singapore522261425926258952468132337This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

57%

Seen by 46 of 80 full-feed vantage points

Partially propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
LACNIC — Latin America and the Caribbean
Country
Chile
Allocated
26th July 1993
Allocation block
165.182.0.0/16
Status
assigned
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 165.182.0.0/16: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.165.182.0.0/16AS52226This prefix165.182.45.0/24AS52226165.182.46.0/24AS52226165.182.47.0/24AS52226165.182.49.0/24AS52226165.182.160.0/24AS52226+16 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

No less specific announcement covers this prefix.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS642912th August 2026 present
  2. AS5222612th August 2026 present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 165.182.0.0/16 in the calculator/16 reference

Routing data derived from RouteViews MRT archives and public registry data.