SUBNET.IM

159.90.0.0/16

At a glance

Addresses

65,536

/16 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICVE

Allocated 30th March 1992

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 159.90.0.0/16, fanning out from AS11694 toward the vantage points that see it. Each path is written out in full beneath the graph.AS11694Universidad Simon…OriginAS11562Net Uno, C.A.AS52320V.tal (GlobeNet)AS8529Zain Omantel Inte…AS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS20130Depaul UniversityAS6461Zayo BandwidthAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK1169411562523208529This path
  2. Singapore116941156252320132337This path
  3. Amsterdam1169411562523206939213151This path
  4. Oregon, US116941156252320693920130This path
  5. Sao Paulo11694115625232064613356266213This 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

99%

Seen by 79 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
Venezuela
Allocated
30th March 1992
Allocation block
159.90.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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 159.90.0.0/16
PrefixAddressesOriginVisibility
159.91.0.0/1665.5kAS21976NJEDge.Net, Inc.80/80

History

  1. AS1169412th 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 159.90.0.0/16 in the calculator/16 reference

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