subnet.im

175.158.128.0/18

At a glance

Addresses

16,384

/18 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICNC

Allocated 19th January 2010

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 175.158.128.0/18 as seen from Oregon, US, read outward from the origin: AS56089 → AS18200 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS56089OFFRATELOriginAS18200Office des Postes…AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS56089seen on 621 paths from 141 vantage points
  2. Peer of AS18200seen on 267 paths from 10 vantage points
  3. Peer of AS6939seen on 975,334 paths from 1 vantage point
  4. 4AS20130Depaul UniversityUSVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore560891820038195132337This path
  2. Oregon, US5608918200693920130Shown above
  3. Amsterdam560891820017434549213151This path
  4. London, UK560891820017412998529This path
  5. Sao Paulo56089182001743356266213This 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
APNIC — Asia-Pacific
Country
New Caledonia
Allocated
19th January 2010
Allocation block
175.158.128.0/18
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 175.158.128.0/18
ROA prefixAuthorised originMax length
175.158.128.0/18AS56089/18

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 175.158.128.0/18
PrefixAddressesOriginVisibility
175.158.192.0/1816.4kAS10139Smart Broadband, Inc.80/80

History

  1. AS5608912th 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 175.158.128.0/18 in the calculator/18 reference

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