subnet.im

170.168.27.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCHK

Allocated 20th July 1994

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 170.168.27.0/24, fanning out from AS202656 toward the vantage points that see it. Each path is written out in full beneath the graph.AS202656Ivanov Vitaliy Se…OriginAS60672ServerChoice LtdAS2914NTT America, Inc.AS35280F5 Networks SARLAS3356Lumen (Level 3)AS25091IP-Max SAAS8298IPng Networks GmbHAS8966Etisalat (E&)AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul University
  1. London, UK20265660672291435280This path
  2. Sao Paulo20265660672291435280This path
  3. Amsterdam202656606723356250918298This path
  4. Singapore2026566067233568966132337This path
  5. Oregon, US202656606723356693920130This 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 80 of 81 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
Hong Kong SAR China
Allocated
20th July 1994
Allocation block
170.168.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 170.168.27.0/24
ROA prefixAuthorised originMax length
170.168.27.0/24AS202656/24

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 170.168.27.0/24
PrefixAddressesOriginVisibility
170.168.26.0/24256AS202656Ivanov Vitaliy Sergeevich81/81

History

  1. AS20265622nd September 2026 — present
  2. AS5806112th August 2026 — 21st September 2026
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 170.168.27.0/24 in the calculator/24 reference

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