131.100.12.0/22
At a glance
Addresses
/22 block
Visibility
80 of 80 vantage points
RPKI
Registry
BRAllocated 12th August 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS61752seen on 209 paths from 119 vantage points
- Peer of AS264962seen on 151 paths from 76 vantage points
- Peer of AS28210seen on 579 paths from 93 vantage points
- Peer of AS264409seen on 1,485 paths from 1 vantage point
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, US61752693920130This path
- Amsterdam6175226496228210264409213151Shown above
- Sao Paulo6175226496228210264409266213This path
- London, UK617522649622821026440964538529This path
- Singapore6175226496228210264409174132337This 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
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
- 12th August 2014
- Allocation block
- 131.100.12.0/22
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 131.100.12.0/22 | AS61752 | /32 |
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.100.8.0/22 | 1k | AS53065Opcao Telecom | 80/80 |
History
- AS6175212th 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.100.12.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.