154.0.187.0/24
At a glance
Addresses
/24 block
Visibility
47 of 80 vantage points
RPKI
Registry
GAAllocated 30th August 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS37616seen on 1,275 paths from 80 vantage points
- Peer of AS327708seen on 10,166 paths from 142 vantage points
- Peer of AS37662seen on 3,474 paths from 2 vantage points
RW
MU
SGOne 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, UK32770817464538529This path
- Singapore3761632770837662132337Shown above
- Amsterdam37616327708376626939213151This path
- Sao Paulo37616327708376626939266213This path
- Oregon, US32770817432572335220130This 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
59%
Seen by 47 of 80 full-feed vantage points
Partially 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
- AFRINIC — Africa
- Country
- Gabon
- Allocated
- 30th August 2013
- Allocation block
- 154.0.176.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.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.0.184.0/21 | 2k | AS37616Airtel Gabon S.A | 79/80 |
| 154.0.176.0/20 | 4.1k | AS37616Airtel Gabon S.A | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.0.186.0/24 | 256 | AS37616Airtel Gabon S.A | 80/80 |
History
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 154.0.187.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.