78.41.192.0/24
Joint Stock Company Investment Company FINAMAS43527
Joint Stock Company Investment Company FINAMAS209352
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
76 of 80 vantage points
RPKI
Registry
Allocated 16th August 2007
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS43527seen on 380 paths from 76 vantage points
- Peer of AS201706seen on 9,329 paths from 96 vantage points
- Peer of AS9002seen on 33,837 paths from 2 vantage points
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
- Amsterdam4352720170620764213151This path
- London, UK4352720170690028529Shown above
- Sao Paulo435272017063356266213This path
- Singapore4352720170620764132337This path
- Oregon, US43527201706693920130This 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
95%
Seen by 76 of 80 full-feed vantage points
Globally 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 August 2007
- Allocation block
- 78.41.192.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 |
|---|---|---|---|
| 78.41.193.0/24 | 256 | AS209352Joint Stock Company Investment Company FINAM | 80/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 78.41.192.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.