149.40.22.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 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 Sao Paulo.
Seen from Sao Paulo
- Peer of AS28323seen on 1,393 paths from 83 vantage points
- Peer of AS262288seen on 1,990 paths from 125 vantage points
- Peer of AS263009seen on 58,452 paths from 131 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
BROne 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, UK2832326228826300933568529This path
- Sao Paulo283232622882630093356266213Shown above
- Amsterdam2832326228826300917434549213151This path
- Singapore2832326228826300933561299132337This path
- Oregon, US283232622882630093356693920130This 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
100%
Seen by 80 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
- ARIN — North America
- Country
- United States
- Allocated
- 28th January 1992
- Allocation block
- 149.40.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.40.20.0/22 | 1k | AS28323AYKO TECHNOLOGY LTDA | 80/80 |
| 149.40.16.0/20 | 4.1k | AS28323AYKO TECHNOLOGY LTDA | 79/80 |
| 149.40.0.0/16 | 65.5k | AS174Cogent Communications, LLC | 79/80 |
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
- AS2832312th 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 149.40.22.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.