subnet.im

201.50.27.0/24

Boerboel LLCAS30042

At a glance

Addresses

256

/24 block

Visibility

98%

79 of 81 vantage points

RPKI

Invalid

Registry

RIPE NCCAE

Allocated 6th March 2025

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 201.50.27.0/24 as seen from Singapore, read outward from the origin: AS30042 → AS49592 → AS62255 → AS174 → AS132337. Each hop is listed with its network name beneath the graph.AS30042Boerboel LLCOriginAS49592Pipe Networks LTDAS62255BiMajLink d.o.o.AS174Cogent Communicat…AS132337Axclusive

Seen from Singapore

  1. 1AS30042Boerboel LLCUSOrigin
    Peer of AS30042seen on 1,590 paths from 80 vantage points
  2. 2AS49592Pipe Networks LTDGB
    Peer of AS49592seen on 4,061 paths from 143 vantage points
  3. 3AS62255BiMajLink d.o.o.SI
    Peer of AS62255seen on 12,289 paths from 75 vantage points
  4. 4AS174Cogent Communications, LLCUS
    Peer of AS174seen on 77,776 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. London, UK300424959262255129935280This path
  2. Sao Paulo300424959262255129935280This path
  3. Singapore300424959262255174132337Shown above
  4. Oregon, US3004249592622551299693920130This path
  5. Amsterdam30042495926225512993893082838298This 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

98%

Seen by 79 of 81 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 Arab Emirates
Allocated
6th March 2025
Allocation block
201.50.0.0/18
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 201.50.27.0/24
ROA prefixAuthorised originMax length
201.50.26.0/23AS834/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 201.50.27.0/24
PrefixAddressesOriginVisibility
201.50.26.0/24256AS30042Boerboel LLC79/81

History

  1. AS3004226th September 2026 — present
  2. AS21942712th August 2026 — 21st September 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 201.50.27.0/24 in the calculator/24 reference

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