SUBNET.IM

83.136.240.0/21

JSC "ER-Telecom Holding"AS41733

JSC "ER-Telecom Holding"AS31484

Announced by more than one origin AS (MOAS).

At a glance

Addresses

2,048

/21 block

Visibility

71%

57 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 16th April 2004

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 83.136.240.0/21, fanning out from AS31484, AS41733 toward the vantage points that see it. Each path is written out in full beneath the graph.AS41733JSC "ER-Telecom H…OriginAS9049JSC "ER-Telecom H…AS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS31484JSC "ER-Telecom H…OriginAS3267National Research…AS31500Global Network Ma…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS34549meerfarbig GmbH &…AS213151Christian ElsenAS3216Vimpelcom PJSCAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK41733904912998529This path
  2. Singapore31484326731500132337This path
  3. Oregon, US417339049693920130This path
  4. Amsterdam3148432673150034549213151This path
  5. Sao Paulo31484326732163356266213This 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

71%

Seen by 57 of 80 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
Russia
Allocated
16th April 2004
Allocation block
83.136.240.0/21
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 83.136.240.0/21
PrefixAddressesOriginVisibility
83.136.248.0/212kAS202053UpCloud Ltd79/80

History

  1. AS4173312th August 2026 — present
  2. AS3148412th 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 83.136.240.0/21 in the calculator/21 reference

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