subnet.im

45.147.2.0/24

Drugoy Telecom LLCAS201211

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCAE

Allocated 29th August 2019

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 45.147.2.0/24 as seen from Singapore, read outward from the origin: AS201211 → AS12389 → AS4766 → AS132337. Each hop is listed with its network name beneath the graph.AS201211Drugoy Telecom LLCOriginAS12389Rostelecom PJSCAS4766Korea TelecomAS132337Axclusive

Seen from Singapore

  1. 1AS201211Drugoy Telecom LLCRUOrigin
    Peer of AS201211seen on 1,104 paths from 103 vantage points
  2. 2AS12389Rostelecom PJSCRU
    Peer of AS12389seen on 26,029 paths from 1 vantage point
  3. 3AS4766Korea TelecomKR
    Peer of AS4766seen on 70,419 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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, UK201211123898529This path
  2. Amsterdam201211123896939213151This path
  3. Singapore201211123894766132337Shown above
  4. Oregon, US20121112389693920130This path
  5. Sao Paulo2012116076432163356266213This 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
United Arab Emirates
Allocated
29th August 2019
Allocation block
45.147.0.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 45.147.2.0/24
ROA prefixAuthorised originMax length
45.147.2.0/24AS201211/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 45.147.2.0/24
PrefixAddressesOriginVisibility
45.147.3.0/24256AS196695NetOne Rus JSC80/80

History

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

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