subnet.im

153.52.64.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 23rd September 1991

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 153.52.64.0/24 as seen from London, UK, read outward from the origin: AS152179 → AS62610 → AS21859 → AS8529. Each hop is listed with its network name beneath the graph.AS152179GLOBAL COMMUNICAT…OriginAS62610Zenlayer IncAS21859Zenlayer IncAS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS152179seen on 3,408 paths from 76 vantage points
  2. Peer of AS62610seen on 67,595 paths from 139 vantage points
  3. Peer of AS21859seen on 4,370 paths from 130 vantage points

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. Amsterdam15217962610218598298This path
  2. London, UK15217962610218598529Shown above
  3. Sao Paulo1521796261021859129935280This path
  4. Oregon, US1521796261021859855142013This path
  5. Singapore152179626102185942295746323673This 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 76 of 76 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
Germany
Allocated
23rd September 1991
Allocation block
153.52.64.0/18
Status
assigned
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 153.52.64.0/24
ROA prefixAuthorised originMax length
153.52.64.0/24AS152179/24
153.52.64.0/24AS213607/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 153.52.64.0/24
PrefixAddressesOriginVisibility
153.52.65.0/24256AS26383Baxet Group Inc.75/76

History

  1. AS15217915th October 2026 — present
  2. AS21360712th August 2026 — 12th October 2026
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 153.52.64.0/24 in the calculator/24 reference

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