SUBNET.IM

185.52.56.0/23

Recom LLCAS43521

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCRU

Allocated 25th January 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.52.56.0/23 as seen from London, UK, read outward from the origin: AS43521 → AS6856 → AS9002 → AS8529. Each hop is listed with its network name beneath the graph.AS43521Recom LLCOriginAS6856AO IK "Informsvya…AS9002RETN LimitedAS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS43521Recom LLCRUOrigin
    Peer of AS43521seen on 240 paths from 80 vantage points
  2. 2AS6856AO IK "Informsvyaz-Chernozemye"RU
    Peer of AS6856seen on 684 paths from 103 vantage points
  3. 3AS9002RETN LimitedGB
    Peer of AS9002seen on 33,837 paths from 2 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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. Amsterdam43521685620485213151This path
  2. London, UK43521685690028529Shown above
  3. Singapore4352168566939132337This path
  4. Oregon, US435216856693920130This path
  5. Sao Paulo43521685690023356266213This 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 80 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
Russia
Allocated
25th January 2016
Allocation block
185.52.56.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.52.56.0/23
ROA prefixAuthorised originMax length
185.52.56.0/23AS43521/23
185.52.56.0/22AS43521/22

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 185.52.56.0/23: 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.52.56.0/22AS43521185.52.56.0/23AS43521This prefix185.52.58.0/23AS43521

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.52.56.0/23
PrefixAddressesOriginVisibility
185.52.56.0/221kAS43521Recom LLC80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.52.56.0/23
PrefixAddressesOriginVisibility
185.52.58.0/23512AS43521Recom LLC80/80

History

  1. AS4352112th 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.52.56.0/23 in the calculator/23 reference

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