187.6.16.0/21
AS7738 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/21 block
Visibility
76 of 76 vantage points
RPKI
Registry
BRAllocated 28th July 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 AS8167seen on 63,484 paths from 75 vantage points
- Peer of AS7738seen on 206,831 paths from 138 vantage points
- Peer of AS52320seen on 190,217 paths from 83 vantage points
- Peer of AS6461seen on 81,711 paths from 1 vantage point
- Peer of AS8551seen on 1,077,043 paths from 1 vantage point
CO
US
IL
PSOne 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 Paulo8167423035280This path
- Amsterdam816777385232069398298This path
- London, UK816777385232064618529This path
- Singapore8167773852320693923673This path
- Oregon, US81677738523206461855142013Shown 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 76 of 76 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
- LACNIC — Latin America and the Caribbean
- Country
- Brazil
- Allocated
- 28th July 2008
- Allocation block
- 187.6.0.0/17
- 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.
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 |
|---|---|---|---|
| 187.6.0.0/18 | 16.4k | AS8167V.tal | 1/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 187.6.24.0/21 | 2k | AS8167V.tal | 76/76 |
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 187.6.16.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.