47.74.0.0/19
At a glance
Addresses
/19 block
Visibility
79 of 80 vantage points
RPKI
Registry
USAllocated 17th March 2016
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS45102seen on 2,020 paths from 101 vantage points
- Peer of AS17676seen on 5,991 paths from 31 vantage points
- Peer of AS701seen on 26,880 paths from 33 vantage points
- Peer of AS174seen on 181,897 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
JP
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
- Oregon, US45102693920130This path
- London, UK451021767612998529This path
- Sao Paulo4510229143356266213This path
- Amsterdam451021767670117434549213151Shown 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
99%
Seen by 79 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
- 17th March 2016
- Allocation block
- 47.74.0.0/15
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 47.74.0.0/18 | 16.4k | AS45102Alibaba (US) Technology Co., Ltd. | 80/80 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 47.74.0.0/21 | 2k | AS45102Alibaba (US) Technology Co., Ltd. | 80/80 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 47.74.32.0/19 | 8.2k | AS45102Alibaba (US) Technology Co., Ltd. | 80/80 |
History
- AS4510212th 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 47.74.0.0/19 in the calculator/19 reference
Routing data derived from RouteViews MRT archives and public registry data.