SUBNET.IM

195.150.0.0/17

At a glance

Addresses

32,768

/17 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCPL

Allocated 29th August 1996

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
  1. Amsterdam8323196844213151This path
  2. London, UK83231968448529This path
  3. Singapore8323196844132337This path
  4. Oregon, US8323693920130This path
  5. Sao Paulo83231329312993356266213This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Poland
Allocated
29th August 1996
Allocation block
195.150.0.0/16
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 195.150.0.0/17
ROA prefixAuthorised originMax length
195.150.0.0/17AS8323/17
195.150.0.0/16AS8323/16

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 195.150.0.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.195.150.0.0/17AS8323This prefix195.150.48.0/20AS58350195.150.76.0/23AS58350195.150.100.0/24AS206687

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.

More specific announcements

Announcements contained within 195.150.0.0/17
PrefixAddressesOriginVisibility
195.150.48.0/204.1kAS58350PHU Classcom Sp. z o.o.3/80
195.150.76.0/23512AS58350PHU Classcom Sp. z o.o.3/80
195.150.100.0/24256AS206687RESINVEST ENERGY POLSKA Sp. z o.o.79/80

Sibling prefixes

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

History

  1. AS832312th 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 195.150.0.0/17 in the calculator/17 reference

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