201.71.172.0/22
At a glance
Addresses
/22 block
Visibility
79 of 80 vantage points
RPKI
Registry
BRAllocated 18th November 2009
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 AS28635seen on 1,681 paths from 141 vantage points
- Peer of AS262526seen on 5,590 paths from 142 vantage points
- Peer of AS262907seen on 6,089 paths from 102 vantage points
- Peer of AS273683seen on 22,492 paths from 142 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
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
- London, UK2863526252626290727368333568529This path
- Sao Paulo286352625262629072736833356266213Shown above
- Singapore28635262526262907816752320132337This path
- Amsterdam286352625262629078167523206939213151This path
- Oregon, US28635262526262907816752320693920130This 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
99%
Seen by 79 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
- 18th November 2009
- Allocation block
- 201.71.160.0/19
- 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 |
|---|---|---|---|
| 201.71.160.0/20 | 4.1k | AS28635AVATO TECNOLOGIA S.A | 79/80 |
| 201.71.160.0/19 | 8.2k | AS28635AVATO TECNOLOGIA S.A | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 201.71.168.0/22 | 1k | AS28635AVATO TECNOLOGIA S.A | 79/80 |
History
- AS2863512th 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.71.172.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.