subnet.im

201.10.95.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 13th March 2025

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 201.10.95.0/24 as seen from Singapore, read outward from the origin: AS201021 → AS48678 → AS9002 → AS132337. Each hop is listed with its network name beneath the graph.AS201021Ahmet Onur Guney …OriginAS48678Pentech Bilisim T…AS9002RETN LimitedAS132337Axclusive

Seen from Singapore

  1. Peer of AS201021seen on 5,984 paths from 80 vantage points
  2. Peer of AS48678seen on 12,743 paths from 140 vantage points
  3. Peer of AS9002seen on 45,093 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. London, UK2010214867890028529This path
  2. Singapore201021486789002132337Shown above
  3. Sao Paulo2010214867890023356266213This path
  4. Oregon, US201021486789002693920130This path
  5. Amsterdam201021486789002645334549213151This 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
United States
Allocated
13th March 2025
Allocation block
201.10.64.0/19
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 201.10.95.0/24
ROA prefixAuthorised originMax length
201.10.95.0/24AS201021/24
201.10.95.0/24AS48678/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 201.10.95.0/24
PrefixAddressesOriginVisibility
201.10.94.0/24256AS214716WEYRO LTD79/80

History

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

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