38.46.12.0/22
At a glance
Addresses
/22 block
Visibility
11 of 76 vantage points
RPKI
Registry
USAllocated 16th April 1991
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS9294seen on 745 paths from 76 vantage points
- Peer of AS18013seen on 1,966 paths from 76 vantage points
- Peer of AS17476seen on 13,093 paths from 138 vantage points
- Peer of AS2914seen on 207,728 paths from 44 vantage points
- Peer of AS6453seen on 86 paths from 1 vantage point
- Peer of AS7552seen on 9,321 paths from 1 vantage point
- Peer of AS38623seen on 83,119 paths from 1 vantage point
HK
VN
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.
Route visibility
14%
Seen by 11 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 1 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
- 16th April 1991
- Allocation block
- 38.0.0.0/8
- 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 |
|---|---|---|---|
| 38.46.8.0/21 | 2k | AS9294GNET INC. | 76/76 |
| 38.0.0.0/8 | 16.8M | AS174Cogent Communications, LLC | 74/76 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 38.46.12.0/24 | 256 | AS22427GNET INC. | 76/76 |
| 38.46.13.0/24 | 256 | AS22427GNET INC. | 76/76 |
| 38.46.14.0/24 | 256 | AS22427GNET INC. | 76/76 |
| 38.46.15.0/24 | 256 | AS22427GNET INC. | 76/76 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 38.46.8.0/22 | 1k | AS9294GNET INC. | 11/76 |
History
- AS92947th November 2026 — present
- AS92946th November 2026 — 6th November 2026
- AS92941st November 2026 — 3rd November 2026
- AS929429th October 2026 — 31st October 2026
- AS929427th October 2026 — 28th October 2026
- AS929424th October 2026 — 25th October 2026
- AS929424th October 2026 — 24th October 2026
- AS929420th October 2026 — 23rd 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 38.46.12.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.