34.1.32.0/20
At a glance
Addresses
/20 block
Visibility
54 of 80 vantage points
RPKI
Registry
USAllocated 9th May 2022
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS19527seen on 553 paths from 94 vantage points
- Peer of AS1680seen on 693 paths from 2 vantage points
IL
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
- Amsterdam195271680213151Shown above
- London, UK1516912998529This path
- Singapore195271680132337This path
- Oregon, US15169693920130This path
- Sao Paulo1952716803356266213This 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
68%
Seen by 54 of 80 full-feed vantage points
Partially 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
- 9th May 2022
- Allocation block
- 34.0.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 |
|---|---|---|---|
| 34.0.0.0/15 | 131k | AS15169Google LLC | 59/80 |
| 34.0.0.0/15 | 131k | AS19527Google LLC (Google Cloud) | 16/80 |
| 34.0.0.0/15 | 131k | AS43515Google Ireland Limited | 4/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 34.1.48.0/20 | 4.1k | AS15169Google LLC | 26/80 |
| 34.1.48.0/20 | 4.1k | AS19527Google LLC (Google Cloud) | 54/80 |
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 34.1.32.0/20 in the calculator/20 reference
Routing data derived from RouteViews MRT archives and public registry data.