131.161.196.0/22
At a glance
Addresses
/22 block
Visibility
80 of 80 vantage points
RPKI
Registry
BRAllocated 10th October 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS61597seen on 121 paths from 108 vantage points
- Peer of AS52720seen on 3,976 paths from 136 vantage points
- Peer of AS61832seen on 64,760 paths from 137 vantage points
- Peer of AS37468seen on 7,338 paths from 54 vantage points
- Peer of AS4230seen on 81,694 paths from 33 vantage points
- Peer of AS1031seen on 107 paths from 2 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
AO
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
- Oregon, US6159752720693920130This path
- London, UK61597527205255433568529This path
- Sao Paulo6159752720525543356266213This path
- Singapore6159752720618323746842301031132337This path
- Amsterdam615975272061832374684230103134549213151Shown 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
- LACNIC — Latin America and the Caribbean
- Country
- Brazil
- Allocated
- 10th October 2014
- Allocation block
- 131.161.196.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 |
|---|---|---|---|
| 131.161.192.0/22 | 1k | AS264389Conect Ferraz | 79/80 |
History
- AS6159712th 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 131.161.196.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.