44.30.219.0/24
At a glance
Addresses
/24 block
Visibility
75 of 76 vantage points
RPKI
Registry
USAllocated 1st July 1992
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS212532seen on 958 paths from 138 vantage points
- Peer of AS44324seen on 1,181 paths from 137 vantage points
- Peer of AS9515seen on 1,394 paths from 137 vantage points
- Peer of AS62217seen on 1,282 paths from 77 vantage points
- Peer of AS6461seen on 132,858 paths from 5 vantage points
- Peer of AS25091seen on 664,395 paths from 2 vantage points
CN
HK
GB
CHOne 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, UK2125324432495156221764618529This path
- Amsterdam212532443249515622176461250918298Shown above
- Sao Paulo212532443249515622173257645335280This path
- Singapore212532443249515622173257335623673This path
- Oregon, US212532443249515622176461855142013This 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
99%
Seen by 75 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
- United States
- Allocated
- 1st July 1992
- Allocation block
- 44.0.0.0/9
- 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 |
|---|---|---|---|
| 44.0.0.0/9 | 8.4M | AS7377University of California, San Diego | 75/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
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 44.30.219.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.