subnet.im

23.19.53.0/24

At a glance

Addresses

256

/24 block

Visibility

20%

16 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 25th April 2011

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 23.19.53.0/24 as seen from Singapore, read outward from the origin: AS136988 → AS2764 → AS4826 → AS132337. Each hop is listed with its network name beneath the graph.AS136988LEASEWEB AUSTRALI…OriginAS2764AAPT LimitedAS4826Vocus Connect Int…AS132337Axclusive

Seen from Singapore

  1. Peer of AS136988seen on 410 paths from 76 vantage points
  2. Peer of AS2764seen on 99,274 paths from 138 vantage points
  3. Peer of AS4826seen on 6,178 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. Amsterdam2875316265213151This path
  2. London, UK205544162658529This path
  3. Sao Paulo191483356266213This path
  4. Singapore13698827644826132337Shown above
  5. Oregon, US3261332572335220130This 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

20%

Seen by 16 of 80 full-feed vantage points

Seen by few vantage points

Observed at 2 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
ARIN — North America
Country
United States
Allocated
25th April 2011
Allocation block
23.19.52.0/22
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 23.19.53.0/24
ROA prefixAuthorised originMax length
23.19.53.0/24AS133752/24
23.19.53.0/24AS134351/24
23.19.53.0/24AS136988/24
23.19.53.0/24AS19148/24
23.19.53.0/24AS205544/24
23.19.53.0/24AS27411/24
23.19.53.0/24AS28753/24
23.19.53.0/24AS30633/24
23.19.53.0/24AS32613/24
23.19.53.0/24AS393886/24
23.19.53.0/24AS394380/24
23.19.53.0/24AS395954/24
23.19.53.0/24AS396190/24
23.19.53.0/24AS396362/24
23.19.53.0/24AS59253/24
23.19.53.0/24AS60781/24
23.19.53.0/24AS7203/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.

History

  1. AS39595412th August 2026 present
  2. AS5925312th August 2026 present
  3. AS6078112th August 2026 present
  4. AS39619012th August 2026 present
  5. AS1914812th August 2026 present
  6. AS13375212th August 2026 present
  7. AS2875312th August 2026 present
  8. AS13698812th 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 23.19.53.0/24 in the calculator/24 reference

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