187.45.131.0/24
At a glance
Addresses
/24 block
Visibility
79 of 80 vantage points
RPKI
Registry
BRAllocated 5th March 2009
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS28136seen on 79 paths from 79 vantage points
- Peer of AS272551seen on 82 paths from 82 vantage points
- Peer of AS266534seen on 210 paths from 133 vantage points
- Peer of AS28283seen on 21,393 paths from 68 vantage points
- Peer of AS8167seen on 174,578 paths from 142 vantage points
- Peer of AS52320seen on 213,520 paths from 71 vantage points
- Peer of AS6939seen on 309,709 paths from 2 vantage points
CO
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 Paulo28136272551266534266213This path
- Singapore28136272551266534132337This path
- London, UK28136272551266534282838529This path
- Amsterdam28136272551266534282838167523206939213151Shown above
- Oregon, US2813627255126653428283816752320693920130This 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
- 5th March 2009
- Allocation block
- 187.45.128.0/20
- 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 |
|---|---|---|---|
| 187.45.130.0/24 | 256 | AS28136SPACnet - Projetos Avançados em Computação | 78/80 |
History
- AS2813612th 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 187.45.131.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.