subnet.im

62.233.47.0/24

LLC Avtodor-TollRoadsAS20698

MasterTelAS29226

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

88%

71 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCSC

Allocated 13th October 2021

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 62.233.47.0/24 as seen from Amsterdam, read outward from the origin: AS20698 → AS12389 → AS6939 → AS8298. Each hop is listed with its network name beneath the graph.AS20698LLC Avtodor-TollR…OriginAS12389Rostelecom PJSCAS6939Hurricane Electri…AS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS20698seen on 168 paths from 75 vantage points
  2. Peer of AS12389seen on 488,060 paths from 117 vantage points
  3. Peer of AS6939seen on 130,956 paths from 2 vantage points
  4. 4AS8298IPng Networks GmbHCHVantage 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. Amsterdam206981238969398298Shown above
  2. London, UK2069812389129935280This path
  3. Sao Paulo2069812389693935280This path
  4. Singapore20698123894766132337This path
  5. Oregon, US2069812389693920130This 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

88%

Seen by 71 of 81 full-feed vantage points

Partially 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
Seychelles
Allocated
13th October 2021
Allocation block
62.233.47.0/24
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 62.233.47.0/24
ROA prefixAuthorised originMax length
62.233.47.0/24AS20698/24
62.233.47.0/24AS25515/24
62.233.47.0/24AS29226/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 62.233.47.0/24
PrefixAddressesOriginVisibility
62.233.46.0/24256AS47122CYBERFIRST LLC81/81

History

  1. AS2069822nd September 2026 — present
  2. AS2922624th September 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 62.233.47.0/24 in the calculator/24 reference

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