subnet.im

82.147.66.0/24

Siberian Telecommunications Ltd.AS31112

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 26th February 2004

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 82.147.66.0/24 as seen from Singapore, read outward from the origin: AS31112 → AS204298 → AS12389 → AS4766 → AS132337. Each hop is listed with its network name beneath the graph.AS31112Siberian Telecomm…OriginAS204298AO TODEPAS12389Rostelecom PJSCAS4766Korea TelecomAS132337Axclusive

Seen from Singapore

  1. 1AS31112Siberian Telecommunications Ltd.RUOrigin
    Peer of AS31112seen on 79 paths from 79 vantage points
  2. 2AS204298AO TODEPRU
    Peer of AS204298seen on 43 paths from 30 vantage points
  3. 3AS12389Rostelecom PJSCRU
    Peer of AS12389seen on 26,029 paths from 1 vantage point
  4. 4AS4766Korea TelecomKR
    Peer of AS4766seen on 70,419 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, UK31112204298123898529This path
  2. Amsterdam3111220429832166663213151This path
  3. Sao Paulo3111220429832163356266213This path
  4. Singapore31112204298123894766132337Shown above
  5. Oregon, US311122042983216693920130This 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
Russia
Allocated
26th February 2004
Allocation block
82.147.64.0/19
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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 82.147.66.0/24
PrefixAddressesOriginVisibility
82.147.67.0/24256AS57494Adman LLC80/80

History

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

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