41.76.254.0/24
At a glance
Addresses
/24 block
Visibility
23 of 80 vantage points
RPKI
Registry
NGAllocated 16th December 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS37286seen on 23 paths from 23 vantage points
- Peer of AS36940seen on 223 paths from 80 vantage points
- Peer of AS29465seen on 43,594 paths from 142 vantage points
- Peer of AS16637seen on 3,905 paths from 3 vantage points
- Peer of AS13030seen on 196 paths from 2 vantage points
- Peer of AS58299seen on 25,347 paths from 2 vantage points
- Peer of AS41051seen on 25,385 paths from 2 vantage points
ZA
CH
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
- Singapore372863694029465166378966132337This path
- Amsterdam37286369402946516637130305829941051213151Shown above
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
29%
Seen by 23 of 80 full-feed vantage points
Seen by few vantage pointsObserved 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
- AFRINIC — Africa
- Country
- Nigeria
- Allocated
- 16th December 2010
- Allocation block
- 41.76.248.0/21
- 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
No prefix of the same length in the same parent block is announced.
History
- AS3728612th 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 41.76.254.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.