149.88.87.0/24
At a glance
Addresses
/24 block
Visibility
9 of 76 vantage points
RPKI
Registry
USAllocated 28th January 1992
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS401701seen on 4,606 paths from 76 vantage points
- Peer of AS40779seen on 490 paths from 9 vantage points
- Peer of AS4635seen on 2,155 paths from 20 vantage points
- Peer of AS9304seen on 2,043 paths from 1 vantage point
- Peer of AS38623seen on 83,119 paths from 1 vantage point
HK
KHOne 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
- Singapore40170140779463593043862323673Shown above
- Sao Paulo401701407794635930423764771335280This 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
12%
Seen by 9 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 3 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
- ARIN — North America
- Country
- United States
- Allocated
- 28th January 1992
- Allocation block
- 149.88.0.0/16
- 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 |
|---|---|---|---|
| 149.88.84.0/22 | 1k | AS401696cognetcloud INC | 1/76 |
| 149.88.80.0/21 | 2k | AS401696cognetcloud INC | 76/76 |
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
- AS4017017th November 2026 — present
- AS4017016th November 2026 — 6th November 2026
- AS4017015th November 2026 — 5th November 2026
- AS4017014th November 2026 — 4th November 2026
- AS4017013rd November 2026 — 3rd November 2026
- AS4017012nd November 2026 — 2nd November 2026
- AS4017011st November 2026 — 1st November 2026
- AS40170131st October 2026 — 31st October 2026
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 149.88.87.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.