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
/21 block
Visibility
57 of 80 vantage points
RPKI
Registry
RUAllocated 16th April 2004
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS31484seen on 92 paths from 23 vantage points
- Peer of AS3267seen on 9,464 paths from 110 vantage points
- Peer of AS31500seen on 1,734 paths from 2 vantage points
AG
SGOne 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
- London, UK41733904912998529This path
- Singapore31484326731500132337Shown above
- Oregon, US417339049693920130This path
- Amsterdam3148432673150034549213151This path
- 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 propagatedObserved 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 83.136.248.0/21 | 2k | AS202053UpCloud Ltd | 79/80 |
History
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.