201.7.167.0/24
At a glance
Addresses
/24 block
Visibility
78 of 80 vantage points
RPKI
Registry
BRAllocated 24th April 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS263290seen on 139 paths from 139 vantage points
- Peer of AS263508seen on 139 paths from 97 vantage points
- Peer of AS53181seen on 44,654 paths from 138 vantage points
- Peer of AS13786seen on 10,089 paths from 30 vantage points
- Peer of AS3257seen on 96,683 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
US
DEOne 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 Paulo263290263508266181266213This path
- London, UK26329026350826618133568529This path
- Singapore2632902635082661816939132337This path
- Oregon, US263290263508266181693920130This path
- Amsterdam2632902635085318113786325734549213151Shown 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
98%
Seen by 78 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
- LACNIC — Latin America and the Caribbean
- Country
- Brazil
- Allocated
- 24th April 2014
- Allocation block
- 201.7.164.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 |
|---|---|---|---|
| 201.7.166.0/24 | 256 | AS263290IMUNIDADE DIGITAL SERVICOS EM COMUNICACAO LTDA | 79/80 |
History
- AS26329012th 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 201.7.167.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.