138.185.230.0/24
At a glance
Addresses
/24 block
Visibility
75 of 76 vantage points
RPKI
Registry
BRAllocated 7th July 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS47065seen on 456 paths from 137 vantage points
- Peer of AS12148seen on 667 paths from 138 vantage points
- Peer of AS2722seen on 592 paths from 95 vantage points
- Peer of AS2721seen on 186 paths from 58 vantage points
- Peer of AS3257seen on 41,698 paths from 5 vantage points
- Peer of AS25091seen on 665,606 paths from 2 vantage points
US
CHOne 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, UK470651214827221049012998529This path
- Sao Paulo4706512148272227211116435280This path
- Amsterdam4706512148272227213257250918298Shown above
- Oregon, US47065121482722272132572335220130This path
- Singapore4706512148272227211116446373862323673This 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 75 of 76 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
- 7th July 2015
- Allocation block
- 138.185.228.0/22
- Status
- assigned
- 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 |
|---|---|---|---|
| 138.185.231.0/24 | 256 | AS47065USC / UFMG PEERING Research Testbed | 75/76 |
History
- AS4706522nd September 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 138.185.230.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.