45.234.216.0/24
At a glance
Addresses
/24 block
Visibility
78 of 80 vantage points
RPKI
Registry
BRAllocated 12th April 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS267393seen on 78 paths from 78 vantage points
- Peer of AS52626seen on 1,144 paths from 140 vantage points
- Peer of AS267059seen on 1,723 paths from 140 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 148,979 paths from 2 vantage points
US
AEOne 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
- Amsterdam267393526262670592625262629078167523206939→ ⋯This path
- London, UK2673935262626705926252626290727368333568529Shown above
- Sao Paulo26739352626267059262526262907816752320266213This path
- Singapore26739352626267059262526262907816752320132337This path
- Oregon, US267393526262670592625262629078167523206939→ ⋯This 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
98%
Seen by 78 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 April 2018
- Allocation block
- 45.234.216.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 |
|---|---|---|---|
| 45.234.217.0/24 | 256 | AS267393ACCESS INTERNET | 78/80 |
History
- AS26739312th 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 45.234.216.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.