189.39.185.0/24
At a glance
Addresses
/24 block
Visibility
55 of 80 vantage points
RPKI
Registry
BRAllocated 8th June 2020
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 AS2seen on 23 paths from 23 vantage points
- Peer of AS270792seen on 100 paths from 62 vantage points
- Peer of AS271023seen on 1,870 paths from 129 vantage points
- Peer of AS13786seen on 3,601 paths from 17 vantage points
- Peer of AS6939seen on 975,334 paths from 1 vantage point
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
- Sao Paulo27079226734711432266213This path
- Singapore270792268824266166132337This path
- Amsterdam2707922688242661666057213151This path
- London, UK27079226882426616660578529This path
- Oregon, US227079227102313786693920130Shown 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
69%
Seen by 55 of 80 full-feed vantage points
Partially 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
- LACNIC — Latin America and the Caribbean
- Country
- Brazil
- Allocated
- 8th June 2020
- Allocation block
- 189.39.184.0/22
- 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 |
|---|---|---|---|
| 189.39.184.0/24 | 256 | AS270792Link Net | 78/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 189.39.185.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.