subnet.im

78.40.119.0/24

Aleksandr ButenkoAS50015

At a glance

Addresses

256

/24 block

Visibility

88%

70 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 19th June 2018

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 78.40.119.0/24 as seen from Singapore, read outward from the origin: AS50015 → AS199961 → AS48084 → AS31133 → AS132337. Each hop is listed with its network name beneath the graph.AS50015Aleksandr ButenkoOriginAS199961Multitelesystems …AS48084Uzhnie Magistralj…AS31133MegaFon PJSCAS132337Axclusive

Seen from Singapore

  1. 1AS50015Aleksandr ButenkoRUOrigin
    Peer of AS50015seen on 99 paths from 33 vantage points
  2. 2AS199961Multitelesystems LLCRU
    Peer of AS199961seen on 1,693 paths from 140 vantage points
  3. 3AS48084Uzhnie Magistraljnie Linii Svyazi LLCRU
    Peer of AS48084seen on 2,365 paths from 77 vantage points
  4. 4AS31133MegaFon PJSCRU
    Peer of AS31133seen on 2,450 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, UK50015488824750290028529This path
  2. Singapore500151999614808431133132337Shown above
  3. Oregon, US500151999614320135598693920130This path
  4. Amsterdam50015488824750290023356645334549213151This 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 70 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
19th June 2018
Allocation block
78.40.116.0/22
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 78.40.119.0/24
PrefixAddressesOriginVisibility
78.40.118.0/24256AS215279OOO Bazis80/80

History

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

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