subnet.im

185.52.119.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCIQ

Allocated 1st April 2014

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.119.0/24 as seen from London, UK, read outward from the origin: AS57324 → AS208293 → AS211513 → AS212573 → AS35313 → AS8529. Each hop is listed with its network name beneath the graph.AS57324Al Lawn Al Akhdar…OriginAS208293AlSalam State Com…AS211513Al Lawn Al Akhdar…AS212573FastIraq, LLCAS35313Infonas W.L.L.AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS57324seen on 2,208 paths from 80 vantage points
  2. Peer of AS208293seen on 15,230 paths from 142 vantage points
  3. Peer of AS211513seen on 247 paths from 79 vantage points
  4. Peer of AS212573seen on 62 paths from 62 vantage points
  5. Peer of AS35313seen on 7 paths from 1 vantage 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. Amsterdam5732420829321151321257335313213151This path
  2. London, UK57324208293211513212573353138529Shown above
  3. Singapore5732420829321151321257335313132337This path
  4. Sao Paulo57324208293211513212573212773356266213This path
  5. Oregon, US5732420829321151321257335313693920130This 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
Iraq
Allocated
1st April 2014
Allocation block
185.52.116.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.119.0/24
ROA prefixAuthorised originMax length
185.52.119.0/24AS56484/24
185.52.119.0/24AS57324/24
185.52.116.0/22AS210001/22
185.52.116.0/22AS212573/22
185.52.116.0/22AS56484/22

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 185.52.119.0/24
PrefixAddressesOriginVisibility
185.52.118.0/24256AS57324Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.80/80

History

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

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