45.231.45.0/24
At a glance
Addresses
/24 block
Visibility
75 of 80 vantage points
RPKI
Registry
MXAllocated 9th February 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS255546seen on 75 paths from 75 vantage points
- Peer of AS265546seen on 252 paths from 79 vantage points
- Peer of AS13999seen on 145,997 paths from 142 vantage points
- Peer of AS32098seen on 54,444 paths from 101 vantage points
- Peer of AS174seen on 181,897 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
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
- London, UK25554626554613999320981374098529This path
- Amsterdam255546265546139993209817434549213151Shown above
- Sao Paulo255546265546139993209829143356266213This path
- Singapore255546265546139993209829148966132337This path
- Oregon, US255546265546139993209832572335220130This 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
94%
Seen by 75 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
- Mexico
- Allocated
- 9th February 2018
- Allocation block
- 45.231.44.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 |
|---|---|---|---|
| 45.231.44.0/24 | 256 | AS265546HYUNDAI AUTOEVER MEXICO, S. DE R.L. DE CV | 80/80 |
History
- AS25554612th 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.231.45.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.