195.19.70.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
RUAllocated 29th October 1996
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS44310seen on 122 paths from 78 vantage points
- Peer of AS25549seen on 2,260 paths from 88 vantage points
- Peer of AS9049seen on 89,204 paths from 109 vantage points
- Peer of AS9002seen on 185,530 paths from 99 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
GB
US
BROne 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, UK44310123898529This path
- Amsterdam44310123896939213151This path
- Singapore44310123894766132337This path
- Oregon, US4431012389693920130This path
- Sao Paulo4431025549904990023356266213Shown above
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
100%
Seen by 80 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
- 29th October 1996
- Allocation block
- 195.19.64.0/18
- 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 |
|---|---|---|---|
| 195.19.71.0/24 | 256 | AS44310INTERNET TECHNOLOGIES LLC | 80/80 |
History
- AS4431012th 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.19.70.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.