subnet.im

195.78.104.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 5th October 2009

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 195.78.104.0/24 as seen from Oregon, US, read outward from the origin: AS50015 → AS199961 → AS43201 → AS35598 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS50015Aleksandr ButenkoOriginAS199961Multitelesystems …AS43201Telematika LLCAS35598INETCOM CARRIER L…AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. 1AS50015Aleksandr ButenkoRUOrigin
    Peer of AS50015seen on 99 paths from 33 vantage points
  2. 2AS199961Multitelesystems LLCRU
    Peer of AS199961seen on 377 paths from 49 vantage points
  3. 3AS43201Telematika LLCRU
    Peer of AS43201seen on 1,792 paths from 69 vantage points
  4. 4AS35598INETCOM CARRIER LLCRU
    Peer of AS35598seen on 54,022 paths from 94 vantage points
  5. 5AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 975,334 paths from 1 vantage point
  6. 6AS20130Depaul UniversityUSVantage 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. Singapore500151999614808431133132337This path
  3. Oregon, US500151999614320135598693920130Shown above
  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
5th October 2009
Allocation block
195.78.104.0/23
Status
assigned
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 195.78.104.0/24
PrefixAddressesOriginVisibility
195.78.105.0/24256AS50015Aleksandr Butenko70/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 195.78.104.0/24 in the calculator/24 reference

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