146.19.183.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
TJAllocated 17th November 2021
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 AS60101seen on 66 paths from 66 vantage points
- Peer of AS208592seen on 5,425 paths from 82 vantage points
- Peer of AS8449seen on 8,061 paths from 106 vantage points
- Peer of AS28910seen on 2,632 paths from 28 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
KG
UZ
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, UK6010120859284492891012998529This path
- Sao Paulo601012085928449289103356266213Shown above
- Singapore6010120859284492891020764132337This path
- Amsterdam60101208592844928910123896939213151This path
- Oregon, US6010120859284492891012389693920130This 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
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
- Tajikistan
- Allocated
- 17th November 2021
- Allocation block
- 146.19.183.0/24
- 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 |
|---|---|---|---|
| 146.19.182.0/24 | 256 | AS7393CYBERCON, INC. | 79/80 |
History
- AS6010112th 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 146.19.183.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.