199.19.21.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
CAAllocated 1st October 2026
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS214933seen on 117 paths from 117 vantage points
- Peer of AS44324seen on 10,349 paths from 139 vantage points
- Peer of AS140227seen on 6,908 paths from 134 vantage points
- Peer of AS137409seen on 4,635 paths from 1 vantage point
- Peer of AS8551seen on 1,077,002 paths from 1 vantage point
CN
US
HK
AU
IL
PSOne 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, UK2149331743369398529This path
- Singapore2149334432414022723673This path
- Amsterdam214933443241402271374098298This path
- Sao Paulo214933174331741295635280This path
- Oregon, US21493344324140227137409855142013Shown 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
100%
Seen by 76 of 76 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
- Canada
- Allocated
- 1st October 2026
- Allocation block
- 199.19.20.0/22
- 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.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 199.19.20.0/24 | 256 | AS210352Yijia Xu | 76/76 |
History
- AS2149336th October 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 199.19.21.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.