subnet.im

158.173.201.0/24

At a glance

Addresses

256

/24 block

Visibility

32%

25 of 77 vantage points

RPKI

Invalid

Registry

RIPE NCCNL

Allocated 1st September 1993

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 158.173.201.0/24 as seen from Singapore, read outward from the origin: AS62240 → AS2914 → AS23673. Each hop is listed with its network name beneath the graph.AS62240Clouvider LimitedOriginAS2914NTT America, Inc.AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS62240seen on 53,439 paths from 100 vantage points
  2. Peer of AS2914seen on 78,227 paths from 1 vantage 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. Singapore62240291423673Shown above

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.

Route visibility

32%

Seen by 25 of 77 full-feed vantage points

Seen by few vantage points

Observed at 3 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
Netherlands
Allocated
1st September 1993
Allocation block
158.173.128.0/17
Status
assigned
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 158.173.201.0/24
ROA prefixAuthorised originMax length
158.173.201.0/24AS212238/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 158.173.201.0/24
PrefixAddressesOriginVisibility
158.173.200.0/24256AS206092F.N.S. HOLDINGS LIMITED77/77

History

  1. AS6224028th September 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 158.173.201.0/24 in the calculator/24 reference

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