SUBNET.IM

152.175.8.0/24

At a glance

Addresses

256

/24 block

Visibility

46%

37 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCHK

Allocated 23rd May 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: 3 observed paths to 152.175.8.0/24, fanning out from AS209554 toward the vantage points that see it. Each path is written out in full beneath the graph.AS209554ISIF OUOriginAS49304SAKURA LINK LIMIT…AS9516SAKURA LINK LIMIT…AS4229Zenlayer IncAS132337AxclusiveAS21859Zenlayer IncAS4635HKIX Route ServersAS6939Hurricane Electri…AS20130Depaul UniversityAS58299Openfactory GmbH …AS41051Freetransit Proje…
  1. Singapore2095544930495164229132337This path
  2. Oregon, US209554493049516218594635693920130This path
  3. Amsterdam20955449304951621859463569395829941051→ ⋯This 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

46%

Seen by 37 of 80 full-feed vantage points

Partially 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
23rd May 2014
Allocation block
152.175.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 152.175.8.0/24
ROA prefixAuthorised originMax length
152.175.8.0/22AS209554/24
152.175.0.0/17AS8126/24
152.175.0.0/16AS202069/24
152.175.0.0/16AS49304/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 152.175.8.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.152.175.8.0/23AS49304152.175.0.0/16AS202069152.175.8.0/24AS209554This prefix152.175.9.0/24AS209554

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 152.175.8.0/24
PrefixAddressesOriginVisibility
152.175.8.0/23512AS49304SAKURA LINK LIMITED4/80
152.175.0.0/1665.5kAS202069SAKURA INTERNATIONAL INVESTMENT LIMITED80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 152.175.8.0/24
PrefixAddressesOriginVisibility
152.175.9.0/24256AS209554ISIF OU37/80

History

  1. AS20955412th 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 152.175.8.0/24 in the calculator/24 reference

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