subnet.im

159.194.176.0/20

At a glance

Addresses

4,096

/20 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCSC

Allocated 26th May 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.194.176.0/20, fanning out from AS42375 toward the vantage points that see it. Each path is written out in full beneath the graph.AS42375iNet LtdOriginAS51659LLC BaxetAS20764CJSC RASCOMAS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam423755165920764213151This path
  2. London, UK4237551659207648529This path
  3. Singapore423755165920764132337This path
  4. Sao Paulo4237551659207643356266213This path
  5. Oregon, US423755165920764693920130This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Seychelles
Allocated
26th May 1992
Allocation block
159.194.128.0/18
Status
assigned
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 159.194.176.0/20
ROA prefixAuthorised originMax length
159.194.176.0/20AS42375/20

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

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

History

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

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