subnet.im

187.52.38.0/24

AS48538 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 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 London, UK.

OriginVantage point · London, UK
One AS path to 187.52.38.0/24 as seen from London, UK, read outward from the origin: AS219521 → AS6939 → AS8529. Each hop is listed with its network name beneath the graph.AS219521VERSADC VERI MERK…OriginAS6939Hurricane Electri…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Adjacentseen on 16 paths from 6 vantage points
  2. Peer of AS6939seen on 235,210 paths from 8 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. London, UK21952169398529Shown above
  2. Singapore21952169393862323673This path
  3. Amsterdam2195212061194490148498298This path
  4. Sao Paulo2195212061194849645335280This path
  5. Oregon, US2195212061199002855142013This 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
United States
Allocated
13th March 2025
Allocation block
187.52.32.0/20
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 187.52.38.0/24
ROA prefixAuthorised originMax length
187.52.38.0/24AS219521/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 187.52.38.0/24
PrefixAddressesOriginVisibility
187.52.39.0/24256AS206007SG TECH SOLUTIONS SRL75/76

History

  1. AS21952131st October 2026 — present
  2. AS4853815th October 2026 — 23rd 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 187.52.38.0/24 in the calculator/24 reference

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