subnet.im

185.138.52.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 10th February 2016

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 185.138.52.0/24 as seen from London, UK, read outward from the origin: AS48821 → AS137409 → AS8529. Each hop is listed with its network name beneath the graph.AS48821Mauve Mailorder S…OriginAS137409GSL Networks Pty …AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS48821seen on 5 paths from 1 vantage point
  2. Peer of AS137409seen on 91,764 paths from 6 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. Amsterdam48821205112213151This path
  2. London, UK488211374098529Shown above
  3. Oregon, US48821693920130This path
  4. Sao Paulo48821506293356266213This path
  5. Singapore488215062950263132337This 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
Germany
Allocated
10th February 2016
Allocation block
185.138.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 185.138.52.0/24
ROA prefixAuthorised originMax length
185.138.52.0/22AS48821/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 185.138.52.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.185.138.52.0/22AS48821185.138.52.0/24AS48821This prefix185.138.53.0/24AS48821

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 185.138.52.0/24
PrefixAddressesOriginVisibility
185.138.52.0/221kAS48821Mauve Mailorder Software Verwaltung GmbH79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.138.52.0/24
PrefixAddressesOriginVisibility
185.138.53.0/24256AS48821Mauve Mailorder Software Verwaltung GmbH79/80

History

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

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