SUBNET.IM

167.56.160.0/20

Administracion Nacional de TelecomunicacionesAS6057

At a glance

Addresses

4,096

/20 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

LACNICUY

Allocated 31st March 2014

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.

OriginVantage points
AS path graph: 5 observed paths to 167.56.160.0/20, fanning out from AS6057 toward the vantage points that see it. Each path is written out in full beneath the graph.AS6057Administracion Na…OriginAS213151Christian ElsenAS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam6057213151This path
  2. London, UK60578529This path
  3. Sao Paulo6057266213This path
  4. Singapore6057132337This path
  5. Oregon, US6057693920130This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally 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
Uruguay
Allocated
31st March 2014
Allocation block
167.56.0.0/13
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 167.56.160.0/20
ROA prefixAuthorised originMax length
167.56.0.0/13AS6057/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 167.56.160.0/20: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.167.56.0.0/13AS6057167.56.160.0/20AS6057This prefix167.56.176.0/20AS6057

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

Announcements that contain 167.56.160.0/20
PrefixAddressesOriginVisibility
167.56.0.0/13524kAS6057Administracion Nacional de Telecomunicaciones79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 167.56.160.0/20
PrefixAddressesOriginVisibility
167.56.176.0/204.1kAS6057Administracion Nacional de Telecomunicaciones80/80

History

  1. AS605712th 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 167.56.160.0/20 in the calculator/20 reference

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