95.46.64.0/21
At a glance
Addresses
/21 block
Visibility
80 of 80 vantage points
RPKI
Registry
CZAllocated 1st December 2008
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS57764seen on 800 paths from 80 vantage points
- Peer of AS28910seen on 14,067 paths from 118 vantage points
- Peer of AS12389seen on 526,463 paths from 116 vantage points
- Peer of AS6939seen on 975,334 paths from 1 vantage point
UZ
RU
USOne 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, UK577642891064538529This path
- Amsterdam5776428910123896939213151This path
- Sao Paulo577642891032163356266213This path
- Singapore5776428910123894766132337This path
- Oregon, US577642891012389693920130Shown 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
- Czechia
- Allocated
- 1st December 2008
- Allocation block
- 95.46.0.0/15
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 95.46.0.0/15 | 131k | AS44546ALFA TELECOM s.r.o. | 80/80 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 95.46.66.0/24 | 256 | AS57764Flink Ltd. | 80/80 |
| 95.46.67.0/24 | 256 | AS57764Flink Ltd. | 80/80 |
| 95.46.68.0/24 | 256 | AS57764Flink Ltd. | 80/80 |
| 95.46.69.0/24 | 256 | AS57764Flink Ltd. | 80/80 |
| 95.46.70.0/24 | 256 | AS57764Flink Ltd. | 80/80 |
| 95.46.71.0/24 | 256 | AS57764Flink Ltd. | 80/80 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS5776412th 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 95.46.64.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.